On 31/12/2014 13:35, Greg Wilkins wrote:
>
> On 23 December 2014 at 16:02, Mark Thomas <markt_at_apache.org
> <mailto: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.
+1. While Tomcat has a gzip filter in the examples, it is there purely
as an example. The 'real' compression implementation is also much lower
down.
> Perhaps there needs to be some standards support for
> activating/delegating such concerns to the container?
I like it. Apart from compression, what other concerns did you have in mind?
Mark