> > > This is the biggest piece of alchemy in my changes. Its also something > > > that has a very good effect - without this nodes with lots of references > > > are dropped as quickly as nodes with one or two. Think NG routing will > > > benifit from something very much like this. > > > > NGrouting will, in a sense, figure this out for itself - hopefully we > > won't need to use alchemy to force it to happen. > > No it won't. If NGrouting favours open connections, and as a consequence > a few connections stay open forever and everything else is ignored, we > will get *lousy* load handling over the network as a whole. Thus we MUST > NOT implement NGrouting before NIO.
NGRouting will only favor open connections over closed connections if the price of going with a sub-optimal open connection reference is lower than that of going with the optimal non-open connection reference, and if this is the case, then NGRouting is perfectly correct in its decision. If the open-connection node gets overloaded then it will no-longer make sense to route via that node, and NGrouting will route elsewhere. You can't argue with simple market economics, and that is what NGrouting is. Ian. -- Ian Clarke [EMAIL PROTECTED] Coordinator, The Freenet Project http://freenetproject.org/ Founder, Locutus http://locut.us/ Personal Homepage http://locut.us/ian/
pgp00000.pgp
Description: PGP signature
