Brice wrote:
It's mostly for the writing side of things.
Ok I just get this part, while looking at the code. Indeed the
GZipInInterceptor doesn't have a GZipThresholdOutputStream nor a
AbstractThresholdOutputStream exists.
I just looked a the code, well for now the code is a bit obscure.
However on a different view and with my limited understanding, I really
don't get why CXF requires to write gzip interceptors, why couldn't we rely
on the transport layer wether it is jetty or commons-http.
To support it on the server side you can use a servlet filter rather
than the interceptors, but for the client side CXF needs to do the
zipping and setting of all the relevant HTTP headers itself. Before I
upgraded the interceptors to work on the server side as well as the
client I used to use http://sourceforge.net/projects/pjl-comp-filter in
my web.xml.
Ian
--
Ian Roberts | Department of Computer Science
[EMAIL PROTECTED] | University of Sheffield, UK
