filwisher/dear

spooky-at-a-distance, content-addressed, filesystem entanglement

dear's Issues

Passing on messages

I think that arguably the behaviour regarding requests that have already been received varies a lot depending on the type of request. query needs to be throttled, whereas add can just pass it on if its new according to the node.

Code needs refactoring

Lots of repeated code and code existing in files that it shouldn't (i.e save code in tcp.go)

We could do we an automated test-suite for some of the longer setups

Setting up a circular loop to test how many echoes are allowed is a very long process

Add pool of clients to request from

Create an abstraction that pools clients and chooses a client for RPC

Not 100% sure which direction to go in

At the moment I'm just setting up basic infrastructure:

RPC for node-to-node communication
content-address saving/retrieving

It's getting a bit scattered though, needs a clearer path
@rjmk

HTML

I'm not sure why we have the HTML? Are we doing a web app? It might be simpler to start on a CLI

Need to fill out README but should maybe decide on CLI interface first?