I remember a statement way back saying that protocol compatability would not be guaranteed until freenet v.1.0.
That being said, it would make freenet far more popular if there was some sort of upgrade tools available for the old nodes. For example, nodes could only talk to nodes of the same version (to incourage stragglers to upgrade) and incompatibilities in the data stores get fixed up on new version installation (e.g. new fields get added with sane defaults, etc.) to avoid all previously inserted data disappearing at to preserve the freenet topography. Mike > Date: Thu, 17 Aug 2000 10:44:25 +0700 > From: Oskar Sandberg <md98-osa at nada.kth.se> > Subject: Re: [Freenet-dev] Associating a public key with node addresses > > Thinking that we will not be forced to break protocol compatibility many > times yet is wishfull thinking. There are still more unresolved then I > care to think about (I have yet to see any particularly encouraging > results out of Serapis). > > Freenet will not be done in a couple of months. It will not be done in a > year and a couple of months either. People who can't wait for that would > best look elsewhere. > > On Wed, Aug 16, 2000 at 07:19:18PM +0100, Ian Clarke wrote: > > I would like to avoid a break in compatability if possible, and it > > seems that we are very close to achieving this. Perhaps allowing 0.4 > > to accept connections from 0.3 nodes if a configuration parameter is > > set to true, and setting this to true by default in 0.4, but to false > > by default in 0.5. > > On that subject, is there really any advantage of using this PK > > mechanism over the current key-exchange algorithm? > > Ian. > > \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
