>> Unless you use http 1.1 and use the persistent TCP connections (forgot
>> the real name, sorry) that do not open a TCP connection for each HTTP
>> request then you are pretty much out of luck. With 1.5 sec RTT, you
>> will get awful performance for HTTP traffic (on the order of
>> 8Kbytes/sec or so). Your best bet is to use one of the available TCP
>> spoofing/proxy boxes and break the end-2-end semantics.
I disagree, based one two things. One is Mark Allman's research on the ACTS
satellite, which I'm sure you're aware of, and the other is the semantics
of HTTP. If you operate in a transaction mode, it really doesn't matter how
many toys you play with, the transactions clock the process - and the
transactions are going across the bird.
It seems to me that the HTTP answer has got to be a combination of
effective use of persistent TCP connections plus the TCP mechanisms -
starting with 2-3 data messages in the first data burst, large windows,
SACK - to make it run well over a high delay*bandwidth link. And I think
ECN is likely to be important as well, although that has much less
operational experience behind it.
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:53 EST