It would certainly be great to get these in if they can be implemented in the next two weeks, but I don't think the release should be delayed if they are not.
Correct me if I am wrong, but all of these can be implemented in a backwards compatable fashion, and I think that under the "release early, release often" mantra, it is more valuable to get the current codebase the wider testing it would receive with a .5 release in about two weeks, than to wait longer and get them in. The most pressing issue for me is resolving the seednodes issue, and making it easier for people to set up non-centralized seednodes. The best thing I can think of for this is the addition of a FCP command which extracts a list of nodes (with a good CP) from the datastore and allows a client to create a seed.txt file which could be uploaded to a website (perhaps automatically). Ian. On Thu, Oct 04, 2001 at 12:08:44PM +0200, Oskar Sandberg wrote: > Probablistic caching :- > Load balancing :- > Address resolution keys :- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20011004/e7f23dc5/attachment.pgp>
