Abstract: Systems, methods, and other embodiments associated with content invalidation are described. One example method includes parsing a response to identify an invalidation directive. Then if identified, invalidating cached content from a cache memory that corresponds to the content identified by an invalidation directive.

Abstract: Systems, methods, and other embodiments associated with content invalidation are described. One example method includes parsing a response to identify an invalidation directive. Then if identified, invalidating cached content from a cache memory that corresponds to the content identified by an invalidation directive.

Abstract: Systems, methods, and other embodiments associated with content invalidation are described. One example method includes providing an invalidation directive in a header of a response.

Abstract: Systems, methodologies, media, and other embodiments associated with processing network communications are described. One embodiment of a method includes processing data requests including changing an input/output (I/O) communications type for processing the data requests.

Abstract: Systems, methods, and other embodiments associated with event logging are described. One example method includes collecting request-based event log data associated with processing a request and temporarily storing the event log data in a memory. In the event of an error, the event log data is transferred to a storage device.

Abstract: Systems, methods, and other embodiments associated with content invalidation are described. One example method includes providing an invalidation directive in a header of a response.

Abstract: Systems, methods, and other embodiments associated with event logging are described. One example method includes collecting request-based event log data associated with processing a request and temporarily storing the event log data in a memory. In the event of an error, the event log data is transferred to a storage device.

Abstract: Systems, methodologies, media, and other embodiments associated with processing network communications are described. One embodiment of a method includes processing data requests including changing an input/output (I/O) communications type for processing the data requests.

Abstract: In a multi-tier data server system, data from the first tier is cached in a mid-tier cache of the middle tier. Access control information from the first tier for the data is also cached within the mid-tier cache. Caching the security information in the middle tier allows the middle tier to make access control decisions regarding requests for data made by clients in the outer tier.

Abstract: A system and method for communicating a side effect of one data request, or other event, as part of a response to another data request or event. The side effect may include notification of the invalidation of cached data, from an upstream cache to a downstream cache. The upstream cache may store invalidation notifications as they are generated or received, and as responses to data requests are sent downstream, piggyback or merge one or more notifications with a response. This scheme avoids the need to open separate communication connections using specified invalidation accounts and passwords.

Abstract: A system and method for communicating a side effect of a data request, from a data server and through one or more caches, inline with a response to the request. Instead of sending a separate notification of the side effect (e.g., instructions to invalidate data cached in one or more caches), the notification is included in the response. As the response traverses caches on its way to the requestor, each cache applies the side effect with the proper timing. Thus, data invalidation may be performed prior to caching data included in the request and/or forwarding the response toward the requester. A final cache configured to serve the response to the requestor may remove the side effect notification before serving the response.

Abstract: A system and method for facilitating the invalidation of cached data, in which the data to be invalidated are identified using information other than a primary key. The primary key for a cached data object, such as a web page, may be a Uniform Resource Locator (URL). Instead of using an object's URL to identify to a cache the data to be invalidated, a secondary key is used, such as the object's data source or a template from which the object was created. An application communicates the secondary key to a cache, and the cache identifies cached objects that match the secondary key. Those data objects are then invalidated without having to issue multiple invalidation messages from the application.

Abstract: A system and method for facilitating the invalidation of cached data, in which the data to be invalidated are identified using information other than a primary key. The primary key for a cached data object, such as a web page, may be a Uniform Resource Locator (URL). Instead of using an object's URL to identify to a cache the data to be invalidated, a secondary key is used, such as the object's data source or a template from which the object was created. An application communicates the secondary key to a cache, and the cache identifies cached objects that match the secondary key. Those data objects are then invalidated without having to issue multiple invalidation messages from the application.

Abstract: A system and method for communicating a side effect of one data request, or other event, as part of a response to another data request or event. The side effect may include notification of the invalidation of cached data, from an upstream cache to a downstream cache. The upstream cache may store invalidation notifications as they are generated or received, and as responses to data requests are sent downstream, piggyback or merge one or more notifications with a response. This scheme avoids the need to open separate communication connections using specified invalidation accounts and passwords.

Abstract: A system and method for communicating a side effect of a data request, from a data server and through one or more caches, inline with a response to the request. Instead of sending a separate notification of the side effect (e.g., instructions to invalidate data cached in one or more caches), the notification is included in the response. As the response traverses caches on its way to the requestor, each cache applies the side effect with the proper timing. Thus, data invalidation may be performed prior to caching data included in the request and/or forwarding the response toward the requester. A final cache configured to serve the response to the requestor may remove the side effect notification before serving the response.