> Actually I haven't tried it recently, I was really just thinking about it
logically.
>
> After I establish the connection and respond with 100 continuation, thats
where I would need to tell the browser that every bit of data I respond >
with will be compressed. Not like long polling where the response header is
sent with the payload.
My project
http://code.google.com/p/gwt-comet/ supports deflate (gzip
without headers and trailers) compression. The Content-Encoding: deflate
header is set on the response initially then streamed compressed data is
sent down the HttpServletResponse. To support this I had to modify a
compressor to support flushing the data in its compression buffer properly
which the built in Java compressors do not support.
RZ