A common approach to caching data in Web applications is to use an HTTP
session. A business use case that spans multiple HTTP requests may create the
need for caching in a Web tier. Once business use–case processing is
completed, this cached data needs to be removed. Failure to do this may lead
to memory leakage, which becomes noticeable when a user HTTP session
continues for hours.
The Solution
The following terminology is used in subsequent sections: A use case is a
sequence of steps performed by a user toward realization of a business
requirement. A nested use case is the extension point from the base use case.
The use case context represents the logical starting point of a use case. The
handler is a server-side component responsible for processing HTTP requests.
The cache element is an object, cached during use case processing. The
navigation path is the sequen... (more)