Servlet caching
After a servlet is invoked and generating the output to cache,
a cache entry is created containing the output and the side effects of the
invocation. For example, these side effects can include calls to other servlets
or JavaServer Pages (JSP) files, as well as metadata about the entry, including
timeout and entry priority information.
Unique entries are distinguished by an ID string generated from the HttpServletRequest
object for each invocation of the servlet. You can then base servlet caching
on:
- Request parameters and attributes the URI used to invoke the servlet
- Session information
- Other options, including cookies
Since JSP files are compiled by WebSphere Application Server into servlets,
the dynamic cache function treats them the same, except in specifically documented
situations.

Configuring servlet caching
Searchable topic ID:
cdyn_servletcaching
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/cdyn_servletcaching.html