W3C home > Mailing lists > Public > public-cdf@w3.org > August 2006

Re: [WICD] comments

From: Chris Lilley <chris@w3.org>
Date: Wed, 30 Aug 2006 18:25:43 +0200
Message-ID: <295152189.20060830182543@w3.org>
To: public-cdf@w3.org
Cc: Bert Bos <bert@w3.org>

Hello public-cdf,

 Bert wrote:

> 10) 8.1 Content Encoding
> 
> Must WICD UAs support gzipped content even if the protocol isn't HTTP? 
> On a typical local file system, e.g., it is not possible to indicate 
> the type of a compressed file. The file has one type ("gzipped data"), 
> unlike in HTTP, where it has both a type ("text/html") and an encoding 
> ("gzip").

Yes; there is no restriction in the spec that constrains gzipped content
to only be served over HTTP.

You are correct that a typical file system cannot convey an equivalent
to the encoding parameter (though it can detect this based on magic
numbers, see the gzip RFC) but then again, a typical file system cannot
convey a full media type either (and again, it can detect this based on
various things like Mac filetypes, filename extensions, and so on). This
is the same for other protocols such as ftp.



-- 
 Chris Lilley                    mailto:chris@w3.org
 Interaction Domain Leader
 Co-Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG
Received on Wednesday, 30 August 2006 16:26:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:41 GMT