In the HTTPServlet world, the servlet container gives my servlet the
chance build a response based around the '304 Not Modified' message,
via a long valued integer specifying a last modified time
(getLastModified()). Great stuff, invaluable for servlets which
format some data once and then serve it forever.
Hmm, now I'm into JSP, if I have a JSP page with static HTML and a
single <jsp:include> of a servlet, there seems no way for the JSP page
implementation class to handle this notion of lastModified().
Hmm, the HttpJspPage doesn't even extend HttpServlet so I guess this
functionality isn't planned?
I have perused the JSP 1.1 spec, nothing.
I'm tempted to wrap all my JSP pages inside servlets, using
requestDispatcher.includes()s, so I'll get the 304 options back...
Anyone any comments?
stu
--
Stuart Maclean, Research Associate
University of Washington
ITS Research Program, College of Engineering
Box 352500
Seattle, WA 98195-2500
Tel: (206) 543-0637
http://www.its.washington.edu
___________________________________________________________________________
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
