Could somebody explain when in the request process getLastModified is called on a servlet? Is it before everything - all servlets, filters, listeners, anything else?
If you have multiple filters, how does this fit into the process - are they all guaranteed to see the process through before the getLastModified call occurs on the servlet? (i.e. Can you count on the filtering to have occurred before the code in your getLastModified runs?) I ask in the case that your getLastModified is more than a simple file system last modified timestamp check, and where you're using some kind of controller servlet rather than servlet-per-path - in which case your one getLastModified method in the controller servlet could become complex, having to deal with multiple getLastModified semantics of multiple pages that map to one servlet? With what request methods is it called (GET, POST, etc...)? The servlet spec gives only a slight indication that it's for GETs, but doesn't really elaborate. Thanks. -- View this message in context: http://www.nabble.com/Filters-and-getLastModified-tf4006572.html#a11378442 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
