Abstract: A system and method for caching multiple versions of a data item (e.g., web page, portion of a web page, data table, data object) and determining which of the multiple versions is most responsive to a particular request. A request is received and an initial cache lookup is done with a data identifier (e.g., URL, URI) extracted from the request. If the lookup is unsuccessful (i.e., nothing is returned), the request is passed to an origin server (e.g., web server, data server). If the lookup is successful, it may provide or identify the desired data item (if one version of the data item is served for all requests) or a policy to be applied to determine which version to serve. The cache applies the policy, which identifies the additional parameters, cookies or other information to be considered, and a second lookup is done with the additional information.

Abstract: A multi-tier caching system is provided for a computing device. The system comprises a first cache implemented in operating system or kernel space (e.g., in memory managed by or allocated to an operating system). The system also comprises a second cache implemented in application or user space (e.g., in memory managed by or allocated to an application program). Also provided is a method of operating the multi-tier caching system to serve one type of data from the first cache and a second type of data from the second cache. The first cache may store frequently requested data items and/or those that require little processing of a data request in order to identify a responsive data item. The first cache may also store data items that can be served in response to data requests having different forms, types, parameters, qualifiers or other indicia.

Abstract: The present invention provides an effective and highly scalable mechanism for supporting multiple-request operations (including but not limited to transactions) in a stateless environment, such as the web. A server is used to coordinate the overall processing of client requests. The server performs this coordination function in such a way that: (4) state information associated with multiple-request operations is maintained by the clients making the requests; (5) the clients are unaware that they are maintaining operation-specific state information; and (6) the server itself is not required to persistently maintain the state information, thereby remaining stateless.

Abstract: A session-aware system and method for caching and serving data. A session-aware cache system stores data that may be designated or restricted for service to registered sessions or data requests that include session identifiers. A request for a restricted set of cached data that omits a session identifier is passed to an origin server (e.g., web server, data server) so that a session may be established and a session identifier assigned. The session-aware cache system may determine whether a session identifier of a data request is near expiration. If so, the request may be passed to the origin server so that the session lifetime may be extended.

Abstract: A method and system for processing multiple-request transactions in a stateless environment is provided. A cartridge execution engine intercepts browser messages directed to a cartridge. The cartridge execution engine determines whether the browser messages are associated with transactions. If it is determined that browser messages are associated with transactions, then the cartridge execution engine sends transaction control messages to a transaction manager. In addition, the cartridge execution engine sends operation messages to the cartridge. The cartridge then performs the operations specified in the operation messages. In response to the transaction control messages from the cartridge execution engine, the transaction manager causes the multiple-request transactions to be either committed or rolled back as an atomic unit of work.

Abstract: The present invention provides an effective and highly scalable mechanism for supporting multiple-request operations (including but not limited to transactions) in a stateless environment, such as the web. A server is used to coordinate the overall processing of client requests. The server performs this coordination function in such a way that: (1) state information associated with multiple-request operations is maintained by the clients making the requests; (2) the clients are unaware that they are maintaining operation-specific state information; and (3) the server itself is not required to persistently maintain the state information, thereby remaining stateless.