- From: Jamie Lokier <jamie@shareable.org>
- Date: Mon, 2 Jun 2008 17:31:38 +0100
- To: Henrik Nordstrom <henrik@henriknordstrom.net>
- Cc: Yves Lafon <ylafon@w3.org>, Joe Orton <joe@manyfish.co.uk>, Mark Nottingham <mnot@mnot.net>, Brian Smith <brian@briansmith.org>, ietf-http-wg@w3.org
Henrik Nordstrom wrote: > On mån, 2008-06-02 at 11:31 +0100, Jamie Lokier wrote: > > Yves Lafon wrote: > > > >As already mentioned both gzip and deflate has this property to a > > > >sufficient level. > > > > > > But it is used that way in deployed servers/clients ? Or is chunked > > > encoding always the norm. > > > > Chunked encoding clearly is not the norm when sending compressed > > dynamic content to a HTTP/1.0 client. > > We are talking about transfer-encoding and message delimiting, not > content-encoding. True, but the same message integrity issues w.r.t connection aborts apply to Content-Encoding used for compressed dynamic content. Since that is how it's done most often right now, it seems relevant. -- Jamie > > Regards > Henrik
Received on Monday, 2 June 2008 16:32:21 UTC