Howdy, >What do you think the learning curve is on using filters and would it be
The learning curve for these types of filters (authenticators, loggers) is short and not steep. This is a good place to start: http://www.javaworld.com/javaworld/jw-06-2001/jw-0622-filters.html >worth the effort (dicounting the time/cost factor) to reorganize my design >using proper filters? What would be the major benefits of making this >change? The major benefits would be: - Decoupling of authentication and logging from the business code, and from each other. This really opens up a lot of architecture possibilities when you need to scale up / increase uptime/reliability (e.g. via clustering) etc. - The ability to selectively authenticate certain requests and not others in a clean way. The business code is untouched. - The ability to selectively log different things about different requests in a clean way. - The ability to monitor one set of things for requests, and one different set of things (e.g. content-length) about responses. - You would still be container-independent. - You will have learned about filters and have a clean, easy to understand, easy to maintain design. >One last newby (and possibly very stupid) question...when you write ><filter-class>com.mycompany.MyAuthenticationFilter</filter-class> the >com.mycompany is simply indicating the package that MyAuthenticationFilter >is in, right, or am I completely missing what that indicates. Sorry for It's simply the fully-qualified class name of the servlet class. Your understanding is correct. Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
