Re: SVG12: gzip transfer encoding

Hi Björn,

The WG believes your comment below has been addressed in the reply given to your comment "SVG12: Transfer-Encoding" (http://lists.w3.org/Archives/Public/www-svg/2005Apr/0239.html)

Please reply within two weeks if this reply does not address your concern.
Thanks
/SVG WG

From: Bjoern Hoehrmann <derhoermi@gmx.net <mailto:derhoermi@gmx.net?Subject=Re:%20SVG12:%20gzip%20transfer%20encoding&In-Reply-To=%3C4343e9d3.138341562@smtp.bjoern.hoehrmann.de%3E&References=%3C4343e9d3.138341562@smtp.bjoern.hoehrmann.de%3E> > 
Date: Mon, 18 Apr 2005 00:59:24 +0200
To: www-svg@w3.org <mailto:www-svg@w3.org?Subject=Re:%20SVG12:%20gzip%20transfer%20encoding&In-Reply-To=%3C4343e9d3.138341562@smtp.bjoern.hoehrmann.de%3E&References=%3C4343e9d3.138341562@smtp.bjoern.hoehrmann.de%3E>  
Message-ID: <4343e9d3.138341562@smtp.bjoern.hoehrmann.de> 

 
Dear Scalable Vector Graphics Working Group,
 
  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.
 
regards.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de <http://bjoern.hoehrmann.de> 
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de <http://www.bjoernsworld.de> 
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ <http://www.websitedev.de/>