Re: [freenet-devl] integrating zlib compression into freenet

[Scott G. Miller]

> 
> This is backwards compatible with old clients. They simply can't tell the
> difference between a zip file and a text file which was automatically
> zipped on insert, which is much more reasonable than thinking that zip
> files are actually text files.

I hate to say it but your wrong Brandon.  The content-type of a file
indicates what the file really is, independent of its encoding.  Read the
HTTP spec some time.  (Yes I know, not everyone is a web browser, don't
try that argument, but its not just specifying web browsers).


> 
> Doing it the other way, dispensing with the notion of encoding as
> separate from file types and just having some clients which automatically
> turn text/HTML files into zips and automatically unzip text/HTML files
> allows it to be a totally optional added feature rather than yet another
> thing which a client must do in order to be a properly functioning Freenet
> client.
Thats a bad argument.  If something is downloading an HTML file and doesnt
intend to view it, then there's absolutely no problem with it thinking
that its HTML.

PGP signature