Servlet caching

 

+

Search Tips   |   Advanced Search

 

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
    

 

---