RE: SVG12: gzip transfer encoding

Hi, Bjoern-

Oops. My mistake. This is a separate but superficially similar issue. I will
resend the formal response in the proper thread. (I shouldn't attend telcons
while replying to issues.) 

Regards-
Doug

doug.schepers@vectoreal.com
www.vectoreal.com ...for scalable solutions.
 

Bjoern Hoehrmann wrote:
| 
| * Doug Schepers wrote:
| >|   From 
| http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/conform.html 
| >| 
| >| [...]
| >|   SVG implementations must correctly support gzip-encoded and
| >|   deflate-encoded SVG data streams. SVG implementation that
| >|   support HTTP must support these encodings according to the
| >|   HTTP 1.1 specification [RFC2616]; in particular, the client
| >|   must specify with an "Accept-Encoding:" request header 
| >|   [HTTP-ACCEPT-ENCODING] those encodings that it accepts,
| >|   including at minumum gzip and deflate, and then decompress
| >|   any gzip-encoded and deflate-encoded data streams that are
| >|   downloaded from the server.
| >| [...]
| >| 
| >| Please change the draft such that it is clear whether 
| implementations
| >| are required to support the gzip Transfer-Encoding and if 
| whether they
| >| are required to send the corresponding TE header aswell.
| >
| >We agree that this section could benefit from further clarification. 
| >
| >We have revised this section as follows:
| >
| >"Conforming SVG Servers [...]"
| >
| >Please let us know promptly if you do not feel that this 
| wording addresses
| >your concern.
| 
| It is entirely irrelevant to my concern. I commented on 
| client require-
| ments, and you respond with server requirements. That just 
| doesn't make
| any sense.

Received on Friday, 23 June 2006 19:42:19 UTC