> Orion has released an implementation of servlet 2.3. I haven't had chance to > play with it yet but i am very interested in "Servlet Filtering". I have > been flicking through the new servlet 2.3 api and i think filtering will > address some of the problems with the servlet api. Being able to cleanly > capture the output of a servlet using a filter will be major benifit. I can > forsee being able to implement a caching system for all servlets in a > system. As in all requests go through the filter. > > Does anyone have any thoughts on this? As Craig mentions, an application-level caching scheme is certainly a good use for the new stuff on Filtering that is in the Servlet 2.3 public draft. Some other examples that it will be useful for are: logging or auditing filters, filters that implement some custom authentication scheme, image compression filters, encryption filters, as well as filters that can transform content in some other way - like applying an XSL/T stylesheet to XML output from a servlet, for example. As the web containers become available, we're hoping that the new feature will allow many other kinds of filtering... - Danny Danny Coward Servlet Specification & Web Java Java Software Group, Sun Microsystems [EMAIL PROTECTED] ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
