On Friday 25 July 2003 02:42, Toad wrote: > Various details have led us to the conclusion that NGRouting will not > work effectively unless we implement connection multiplexing first. > Proposal: > > New presentation protocol version representing MUXing mode.
Why is multiplexing on the application protocol level better than just opening a separate TCP session? I would have thought this would not be desirable because it is possible to throttle bandwidth "per TCP session" on some of the fancier routers, which would allow people with control over intermediary routers to throttle Freenet traffic by taking advantage of multiple application sessions going over a single TCP session. I do sort of see a plus point for having only one TCP session to each node, but are multiple TCP sessions really a problem? For example, if a node is twice as fast or twice as useful, why is it a problem to have twice as many TCP connections to it? Additionally, when is the backward compatibility going to be removed? Gordan _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
