On 23 December 2014 at 16:02, Mark Thomas <markt_at_apache.org> wrote:
> For the compression use case, wrapping is the only solution that is
> going to work in all cases.
>
Not any more! Asynchronous IO has made wrapping pretty much a near
impossible task. The complexities of dealing with listeners, isReady etc.
are now too much for a filter.
In Jetty, we have deprecated our GzipFilter and have instead moved
compression to a container mechanism that intercepts output and headers at
a much lower level than filters. I've always thought transport compression
was more of a container concern and less of an application one, so I think
this is a good move.
Perhaps there needs to be some standards support for activating/delegating
such concerns to the container?
--
Greg Wilkins <gregw_at_intalio.com> @ Webtide - *an Intalio subsidiary*
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com advice and support for jetty and cometd.