On Wed, May 02, 2001 at 07:26:13PM -0500, Brandon wrote:
> 
> > I think Tavin gets what I was suggesting here. What do you think Ian?
> > For large text or html files to be both compressed and browsable,
> > zlib compression signified by a meta data field would be most
> > useful. We could start by having only text, html and various other
> > markup languages automatically compressed and decompressed
> > by the client.
> 
> Why not just use the Content-Type field and set it to application/x-gzip?
> Why add another metadata field?

Because that's actually a technically wrong use of Content-Type.  I forget
which RFC I read about this in, but it was one of the HTTP or MIME ones.
Content-Type is supposed to be set to, well, the content type, which is
independent of how the content is encoded .. hence the Transfer-Encoding
header in HTTP.

Think about it, how can the browser distinguish HTML from text or
anything else if you put application/x-gzip in the ContentType?

(btw, in the new metadata standard everything is mixed case with no
 hyphens, i.e. ContentType instead of Content-Type)

-- 

# tavin cole
#
# "The process of scientific discovery is, in effect,
#  a continual flight from wonder."
#                                   - Albert Einstein


_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl

Reply via email to