Abstract: A system and method for searching a bytestream or other string in a case insensitive manner. In a preferred embodiment, the present invention includes an ASCII tree that associated both upper and lower case letters of an incoming header key (or other symbols) with nodes. When enough nodes are gathered, a target word is found.

Abstract: This Sampling Object Cache System (“SOCS”) estimates the size of an in-memory heap-based object cache without the need to serialize every object within the cache. SOCS samples objects at a user-determined rate and then computes a “sample size average” for each type of class—whether a top class, type of top class or non top class. Using these sample size averages, a statistically accurate measure of the overall size of the cache is calculated by adding together the total size of the objects in the cache for each class type.

Abstract: This Sampling Object Cache System (“SOCS”) estimates the size of an in-memory heap-based object cache without the need to serialize every object within the cache. SOCS samples objects at a user-determined rate and then computes a “sample size average” for each type of class—whether a top class, type of top class or non top class. Using these sample size averages, a statistically accurate measure of the overall size of the cache is calculated by adding together the total size of the objects in the cache for each class type.

Abstract: A method of proactively monitoring the coherency of distributed cache. A cache comparison utility selects a set of cache keys from a replica cache connected to a main cache via a network. The cache comparison utility selects a first cache key from the set of cache keys and fetches a first cache value from the replica cache that corresponds to the first cache key. The cache comparison utility generates a first checksum value corresponding to the first cache value and the first cache key and stores the first checksum value in a first checksum table. The cache comparison utility creates a first total checksum value that corresponds to the first checksum table and compares the first total checksum value with multiple total checksum values that correspond to the main cache and one or more additional replica caches, thereby identifying replica caches that are not identical to the main cache.

Abstract: A process for facilitating distribution of asynchronous content by a result server includes subscribing at least one client in response to subscription requests for the asynchronous content received at the result server from the at least one client. The process further includes publishing the asynchronous content. The publishing leads to dissemination of the asynchronous content from the result server to the subscribed clients, and removal of the asynchronous content from the result server. The process further includes receiving a subscription request from additional client(s). The process further includes polling the subscribed clients for the asynchronous content and sending the asynchronous content to the additional client(s) upon receipt of the asynchronous content from any client belonging to the subscribed clients.

Abstract: A system to suggest a directory location in which to save a file. The system includes a client computer and a folder storage locator. The client computer initiates a file save operation. The folder storage locator communicates the suggestion of the directory location in which to save the file. The folder storage locator includes a context identifier, a context analyzer, and a location trigger. The context identifier identifies contextual information of a file in response to a save operation to save the file on a storage device. The context analyzer compares the contextual information of the file to indexing data of an indexing service. The indexing data indexes existing files on the storage device. The location trigger communicates a potential file storage location on the storage device based on the comparison of the contextual information of the file to the indexing data of the indexing service.

Abstract: The ability to leverage a publish/subscribe functionality in an application server environment has allowed the storage of cached entries to be stored over multiple clients rather than on a single application server, freeing up valuable resources. However, in this arrangement it is not possible for the originating server to validate shared content originating from client-side storage. The present invention provides a system and method for securing and validating content from asynchronous include request by allowing a subscribing client to set trusted clients from which they will accept content.

Abstract: This Sampling Object Cache System (“SOCS”) estimates the size of an in-memory heap-based object cache without the need to serialize every object within the cache. SOCS samples objects at a user-determined rate and then computes a “sample size average” for each type of class-whether a top class, type of top class or non top class. Using these sample size averages, a statistically accurate measure of the overall size of the cache is calculated by adding together the total size of the objects in the cache for each class type.

Abstract: Process, apparatus and program product for processing a request at an application server are provided. The process includes initiating one or more asynchronous operations in response to the request received by the application server. The process further includes generating a response content that includes one or more placeholders. Thereafter, one or more placeholders mark a location of content corresponding to each of the one or more asynchronous operations. The process further includes aggregating content received from a completed asynchronous operation by filling the content in the corresponding placeholder. The process further includes sending a partial response content with content up to the first unfilled placeholder.

Abstract: A process for facilitating distribution of asynchronous content by a result server includes subscribing at least one client in response to subscription requests for the asynchronous content received at the result server from the at least one client. The process further includes publishing the asynchronous content. The publishing leads to dissemination of the asynchronous content from the result server to the subscribed clients, and removal of the asynchronous content from the result server. The process further includes receiving a subscription request from additional client(s). The process further includes polling the subscribed clients for the asynchronous content and sending the asynchronous content to the additional client(s) upon receipt of the asynchronous content from any client belonging to the subscribed clients.

Abstract: A method of proactively monitoring the coherency of a distributed cache. A cache comparison utility selects a set of cache keys from a replica cache connected to a main cache via a network. The cache comparison utility selects a first cache key from the set of cache keys and fetches a first cache value from the replica cache that corresponds to the first cache key. The cache comparison utility generates a first checksum value corresponding to the first cache value and the first cache key and stores the first checksum value in a first checksum table. The cache comparison utility creates a first total checksum value that corresponds to the first checksum table and compares the first total checksum value with multiple total checksum values that correspond to the main cache and one or more additional replica caches, thereby identifying replica caches that are not identical to the main cache.