-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
On 10/20/2009 9:47 PM, Mark Thomas wrote: >> Is there a specific reason for this? > > Portability, reduce internal code duplication (filters & valves have a lot in > common) Also, Tomcat has never provided standard request and response wrapper classes for Valves to wrap those objects :( https://issues.apache.org/bugzilla/show_bug.cgi?id=45014 >> Although I love filters, I find that valves have a very specific need within >> the container as well; it allows you to configure the container >> independently of the application. If everything is moving to filters, that >> would require me to modify the app everytime I want the container to behave >> slightly differently. > > Even without valves, there are lots of other ways to customize the > container. You can also specify Filters at the global & host level (may > also add engine to that list). Will there be a way to grab information from the "raw" request as seen by a Valve today? It's nice to be able to get and set values "above" (or below, depending on your POV) the servlet API. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAkrfJJUACgkQ9CaO5/Lv0PA9HACfUfqecyV/Fcx2T18IhypRqVpl ZVUAlAmzCezD2+sTBLvm0atb/VwXadI= =n64M -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
