- From: Fish <fish@infidels.org>
- Date: Thu, 21 Dec 2000 09:51:26 -0800
- To: <www-talk@w3.org>
> Hi, > > Is pipelining supported by any client/server? I mean > sending multiple HTPP GETs or RESPONSEs in a > single TCP segment. > > Thanks, > > Michael I know for a fact that some servers stream their responses back if you stream your requests to it, but I never bothered to make a list. Is that what you're asking? Which specific servers out there (e.g. Apache, Netscape, etc) are actually capable of streaming? If that's your question, I don't know because I never bothered to keep track. I just know some of them do because I've seen it in my trace logs. And which specific clients (i.e. browsers, e.g. Netscape, IE, Opera, etc) stream (pipeline) their requests, I don't know either. I never bothered to check as it's hard to tell from my trace logs (since each HTTP request my proxy processes is handled separately). But if you're asking whether streamed HTTP requests/responses actually get packaged together into the same physical TCP/IP packet, I would venture a guess and answer: "more than likely" (unless you've purposely disabled the Nagle algorithm, which is highly discouraged).[1] -- "Fish" (David B. Trout) fish@infidels.org [1] The Nagle algorithm can be disabled by setting the TCP_NODELAY option for a socket via 'setsockopt'. For more information regarding the Nagle algorithm, see RFC 896.
Received on Thursday, 21 December 2000 12:52:13 UTC