On Wed, 10/15/03 at 20:26:06 +0100, Toad wrote: > > Current unstable -> stable merge first, then multiplexing on unstable > > branch with a split network between unstable and stable might be one way > > to handle this. > > If the unstable code is likely to become good enough to merge before > multiplexing is in... Seems like there are only 3 fairly minor things keeping unstable from merging right now: The weird NPE in RandomFileAccessPool Lock contention in RandomFileAccessPool (probably contributed to or caused by the NPE) FIW not working right.
> > -Allow firewalled nodes to be fully functional parts of the network > > just without ARK insertion. This will give us some of the scalability > > advantages of Gnutella's Ultrapeer technique > You mean shadow nodes? Maybe. I'd rather just set a flag on the > reference and have the node it connects to not forward the reference. That's basically the same thing functionally bunches easier to impliment I guess. > > -Allow us to go back to queueing messages on connections rather than on > > peers, this is probably a good thing as it should help get rid of the > > HUGE message send times that have become a problem on latest unstable. > Not necessarily. The hugeness is merely a diagnostic issue. And I'm not > about to back out PeerHandler. We might have two connections to a node > for some reason or other. Hmm... OK --Brandon _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
