> > Ok, the problem here is that if you have numerous documents all with the > same key then you can't use Freenet's routing mechanism to find all > version, in fact, you can never be sure you have found the latest > version. Further, how can you specify what version you are looking > for? The node which attempts to answer your request probably won't have > all of the versions to start with. This is what both my and Adam's proposals deal with. When you request a document, you receive a list of *all* versions and their CHKs. Then the client picks which he wishes to receive. The server needn't be complicated with versioning any more than just having to add new versions to whatever structure we decide on, a document stack or Adams mappings table (both which I like, but the former requires less coding and is more secure).
> The way I would approach this gives the same functionality, but doesn't > require such an upheaval in the way things operate. Each new version of > a document would be stored under a key like "documentname/0.2", and then > the key "documentname" would redirect to the latest version (this > obviously required that we have implemented data modification and > redirection - both of which are on the radar). Yes, but this lets an adversary steal a version by inserting false data under future version numbers. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
