In a message dated 11/29/2001 10:23:47 AM Pacific Standard Time, [EMAIL PROTECTED] writes:
> > Does the output of mod_deflate have a GZIP and/or ZLIB header on it, or not? > > > Even those 2 headers are NOT the same but that's yet another story. > > Correct. deflate is the algorithm. deflate + gzip header is gzip. > The module should be capable of producing both, if not now then eventually. > > ....Roy Then this is what I am saying... Naming the module after the algorithm ( which isn't even really the actual compression algorithm since it's all just Liv-Zempel 77 prior to IBM/Sperry-Rand patent with some Huffman algos laid in ) would not have been my first choice for a name. If the 'stated goal' of the module is ( as you seem to have just said ) to be able to support just about anything that can appear in an HTTP 'Accept-Encoding:' header then I would have chosen something more to the point like mod_encoding ( So it can do both Content-Encoding and Transfer-Encoding ). Hey... max nix to me. I don't care it it's called mod_lz77_plus_huffman The name doesn't really matter. I'm simply pleased as punch that SOMETHING is finally committed to the Apache CVS tree which is has the potential to 'finally' allow Apache to do parts of the HTTP spec that are over 5 years old now. It's a great step forward. It will 'evolve' and the 'extra' things it needs like cross-header item inclusion/exclusion will be dicated by reality and no one individual but nothing could happen until there is at least something there to 'patch' which satisfies all the myriad Apache submission criteria. Well done. It feels like progress. Yours... Kevin Kiley
