> When those things are done, I'll take on a next project. There isn't > anything else which is sufficiently agreed upon for me to just go ahead > and code it.
Actually I am quite keen on getting updatable data in there - here is my proposal: Basically we need to use PK crypto which is already being integrated into the code. We then need to implement sensible behaviour for the DataUpdate message. I suggest this should search for the data in the usual manner, but then once it finds it's data, it should spread like a virus to "infect" all nodes storing the relevant data. This could be done by a node forwarding the message to the N closest nodes to the key being updated in the datastore. If a node receives a message and it has the data in question, then it updates the data (assuming the update request is signed with the appropriate key), and repeats the process. If a node receives a message and it doesn't store the data locally, then it drops the message. The message should also be dropped if the data has already been updated. This may seem like a drastic and wasteful way to do it - but think about it, remember that to update data we must ensure that *each* node storing the data receives the update. The mechanism I describe should achieve this without too much excess of messages, and thus I think it may be the most efficient way that we can do this. Whether it will work in practice is a different question, but there is really only one good way to find out (ie. suck it and see - the strategy we employed with the original Freenet design!). Ian. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
