W3C home > Mailing lists > Public > www-svg@w3.org > August 2005

Re: SVG12: Transfer-Encoding

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Sun, 21 Aug 2005 12:02:24 -0500
Message-ID: <4308B3A0.6050101@mit.edu>
To: Chris Lilley <chris@w3.org>
CC: Bjoern Hoehrmann <derhoermi@gmx.net>, www-svg@w3.org

Chris Lilley wrote:
> Thanks, that is much clearer. (However, if someone gzips an SVG document,
> the intent is also to speed up network transmission.)

Perhaps.  Or perhaps it's to reduce storage.  Or some other reason.

The litmus test I'd use for content vs transfer encoding is what should happen 
when the user saves the data.  If compressed data should be saved, then content 
encoding is indicated; if uncompressed data should be saved, then transfer 
encoding should be used.

> OK we will clarify for the case where the server compresses on the fly.

Ideally, this would be done by simply deferring to the HTTP/1.1 RFC...

-Boris
Received on Sunday, 21 August 2005 17:03:10 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:31 GMT