> From: Dave Pawson [mailto:[email protected]]
> >> I'm coming down in favour of a valve, rather than a filter,
> >> to make it container specific,
> >
> > Which is a good reason not to use a valve. Unless you need
> access to Tomcat internals, use a filter.
>
> ? Unclear why Charles?
>
> To make it 'filter' all server traffic?
> AFAIK I don't need access to any internals.
Valves only work with Tomcat. Filters work with other servlet containers.
Most of the readers of this list would regard portability between servlet
containers as a Good Thing. Certainly you should be reading the servlet spec
(or a tutorial on it) rather than the Tomcat docs if you want to understand why
Tomcat does a numberof the things it does!
Valves and filters do similar things at the highest level: they intercept the
request and response and allow the valve/filter to do things with those
requests and responses.
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
