- From: Keith Moore <moore@cs.utk.edu>
- Date: Wed, 10 Mar 1999 17:57:32 -0500
- To: Yaron Goland <yarong@microsoft.com>
- cc: "'Keith Moore'" <moore@cs.utk.edu>, web@apps.ietf.org, discuss@apps.ietf.org
> My own experience shows that HTTP works like a champ over wireless. Its > large granularity commands work extremely well over high latency links. TCP doesn't work well over wireless links that have high packet loss rates. Arguably the right way to solve this is with link-layer transmit or FEC, but you don't want to do that for some kinds of traffic. And now that TOS has been deprecated it's not clear (at least to me) how an application can label its packets so that the link layer won't do this. Whether you think HTTP works well over high latency links probably depends on how you use it - especially the granularity of interaction that your application needs. For many applications the TCP connection setup already causes a significant degree of latency. > What issues do you have with HTTP over unicast and multicast UDP? Just the obvious ones. Keith
Received on Wednesday, 10 March 1999 18:09:19 UTC