- From: Henrik Nordstrom <henrik@henriknordstrom.net>
- Date: Mon, 12 May 2008 18:37:11 +0200
- To: Jamie Lokier <jamie@shareable.org>
- Cc: Yves Lafon <ylafon@w3.org>, Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org
On mån, 2008-05-12 at 16:10 +0100, Jamie Lokier wrote: > Are you sure? Concatenating gzip files (.gz) is allowed: when > decompressed it results in the concatenation of the decompressed > parts. Therefore gzip _files_ aren't self delimiting. True. But each part/member is, and if the sender sends a single member it can be sure that the recipient can tell if the message got truncated even if there is no other forms of delimiting. It's the sender that selects to send the message without any other form of delimiting. And in this case the protocol do not really depend on the delimiting being detected proper. The message delimiting is the same as identity encoding without content-length, by closing the connection. But unlike identity encoding the recipient can clearly tell if the message got unexpectedly truncated, with the small exception of a sender sending multiple gzip members in the same stream and the message getting truncated exactly between two members. Regards Henrik
Received on Monday, 12 May 2008 16:38:09 UTC