>> Oren Tirosh <oren@hishome.net> wrote:
>> >An inverse multiplexing layer would be added between the the connection
>> >layer and multiple instances of the transport layer.

>Mark Rafn wrote:
>> Why bother doing this inside the ssh protocol? Wouldn't it be much cleaner
>> to use tcp-level multiplexing and run ssh on top of that (or that on top
>> of SSH tunnels)?

Oren Tirosh <oren@hishome.net> wrote:
>Because of latency. If you build some kind of generic tcp inverse
>multiplexer ("download accelerator") and run ssh over it the total
>throughput will improve but since everything goes through a single
>queue a file transfer over a forwarded port will still hurt the latency
>of your interactive session.

I must be missing something. TCP stacks can include QoS reordering of the
queue, which is pretty much what you'd need to do inside this proposed ssh
extension, isn't it?
--
Mark Rafn dagon@dagon.net <http://www.dagon.net/>