R
Roedy Green
When you are writing Java code to pretend to be a browser, doing HTTP
POSTs and GETs there are four possible Content-Encodings:
deflate: zlib format defined in RFC 1950 plus the deflate compression
mechanism described in RFC 1951.
gzip, alias x-gzip: Java-style gzip RFC 1952 Lempel-Ziv coding with a
32 bit CRC.
compress, alias x-compress, UNIX compress
identity means as-is, no compression. Use in the Content-Request
header, but not the Content-Encoding header. Just leave out the
Content-Encoding if it is identity.
The way I have handled it as ask for identity or gzip, see what comes
back and if necesary fire up GZIP.
So my questions:
1. Can Java be persuaded to do this deflating for you automatically or
semi-automatically.
2. does Java support deflate and compress?
3. what are the relative merits of the three compression schemes?
POSTs and GETs there are four possible Content-Encodings:
deflate: zlib format defined in RFC 1950 plus the deflate compression
mechanism described in RFC 1951.
gzip, alias x-gzip: Java-style gzip RFC 1952 Lempel-Ziv coding with a
32 bit CRC.
compress, alias x-compress, UNIX compress
identity means as-is, no compression. Use in the Content-Request
header, but not the Content-Encoding header. Just leave out the
Content-Encoding if it is identity.
The way I have handled it as ask for identity or gzip, see what comes
back and if necesary fire up GZIP.
So my questions:
1. Can Java be persuaded to do this deflating for you automatically or
semi-automatically.
2. does Java support deflate and compress?
3. what are the relative merits of the three compression schemes?