Erm toad didn't you like say to Reskill that you wouldn't be able to test freenet without letting it run in the wild? How is having a separate test network that isn't backwardly compatible with the current network then forcing a network wide upgrade any different to reverting stable to build 692, with it's own protocol, to keep it from talking to the unstable branch and giving USERS, those people who support the network with payments, a useable network?
Just wondering.... Pete -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Toad Sent: 15 October 2003 19:56 To: [EMAIL PROTECTED] Subject: Re: [freenet-dev] Another Drastic Solution On Wed, Oct 15, 2003 at 07:52:34PM +0100, Toad wrote: > Suggestion: > I implement multiplexing and test it on a local testbed of a few > nodes. I don't implement any kind of backward compatibility. Followed > by a larger testbed of a few volunteers' nodes. Followed by a network > reset - wide deployment, without backward compatibility. When I say wide deployment, I still mean unstable branch - only the crazy people. The stable network is left to rot until the unstable code is ready, and then we merge the unstable code to the stable branch and when users update to stable, they will transition over to the new network. The downside is, of course, that routing will still not have been tested properly on a really large network. HOWEVER given the current state of the network I am willing to concede defeat on that one. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
