On Thu, 16 Oct 2003, Ian Clarke wrote: > 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. > > I am a bit concerned that this is another example of implementing new > features rather than making existing features work properly... :-/
In this case, the feature not working properly is sending messages to other nodes. Due to the arbitrary (alchemy?) low number of sockets common OSs support, we can't send messages due to backlog... and since trailers hop from node-to-node, there's a significant chance that any given trailing field will get "stuck" somewhere along the way. When this happens, it locks a connection _ALL THE WAY BACK_ to the originating DS. What happens when another gets stuck? Or another? Deadlock. So yes, it's "implementing new features" but it's fixing what exists: passing messages through the network. (And it's been discussed for aeons as something that needs to be done) --Dan
pgp00000.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
