W3C home > Mailing lists > Public > www-svg@w3.org > July 2006

Re: SVG12: Transfer-Encoding

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Sat, 22 Jul 2006 01:35:25 +0200
To: <doug.schepers@vectoreal.com>
Cc: <www-svg@w3.org>
Message-ID: <rto2c2hqmbrbfl84ot8ho412r2330n9sgd@hive.bjoern.hoehrmann.de>

* Doug Schepers wrote:

There are a number of missing spaces in the new text.

>Also, if the SVG file is compressed with gzip or deflate, Conforming SVG
>Servers must indicate this with the appropriate header, according to what
>the protocol supports. Specifically, for content compressed by the server
>immediately prior to transfer, the server must use the "Transfer-Encoding:
>gzip" or "Transfer-Encoding: deflate" headers as appropriate, and for
>content stored in a compressed format on the server (i.e.with the file
>extension "svgz"), the server must use the "Content-Encoding: gzip" or
>"Content-Encoding: deflate" headers as appropriate.

The part in (...) does not make sense to me, in particular, the "i.e."
seems incorrect. I suggest to remove this part.

>Note: Compression of stored content (the "entity," in HTTP terms) is
>distinct from automatic compression of the message,as defined in HTTP/1.1
>TE/ Transfer Encoding."

Transfer-Encoding is about transformations applied to the message body,
not to the message as a whole, so this is incorrect aswell. I suggest
the note be removed. Other than that the text seems acceptable.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 21 July 2006 23:42:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:08 UTC