a filter is for filtering requests. a servlet recieves the requests after filters have filtered them. so the servlet should act as the controller. thee is some overlap and some designs make filters do a small part of logic that should be in the controller but no doubt the servlet should be the contoller.
-----Original Message----- From: Bussie, Andre D [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 11, 2004 4:20 PM To: [EMAIL PROTECTED] Subject: Servlet vs. Filter As a best practice what's the best approach a Servlet as the controller or a Filter? Any recommendations? Andre' D. Bussie Sourcing Rotational Program MAC-MAR 532 Fellowship Rd Moorestown, NJ 08057 856.787.3273 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
