- From: Jamie Lokier <jamie@shareable.org>
- Date: Fri, 24 Jul 2009 16:35:58 +0100
- To: Henrik Nordstrom <henrik@henriknordstrom.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Henrik Nordstrom wrote: > * The head of line blocking issue where the processing time (and/or > size) of one response delays all following responses, which can > introduce significant latency. Yes, that's why I advocating multiplexing (based on chunks...), which avoids the problem very effectively. It still suffers from TCP head of line blocking, but that's quite different, much shorter, does not occur on uncongested networks and does not depend on processing time. > * Chunked encoding is quite fragile as message framing method. There is > quite some breakage in that area out on the net, some of which is very > hard to work around when pipelining is enabled. Can you describe these problems? I've not heard of any problem with chunked response encoding, and it's very widely deployed. -- Jamie
Received on Friday, 24 July 2009 15:36:40 UTC