Abstract: A cache server receives a request from a client that includes a requesting entity tag. In turn, the cache server extracts a starting identifier and an ending identifier from the requesting entity tag. The starting identifier is associated with a starting entry and the ending identifier is associated with an ending entry. Next, the cache server determines whether a subsequent entity tag exists that includes a subsequent starting identifier that matches the requesting entity tag's ending identifier. When the cache server identifies a subsequent entity tag, the cache server sends the subsequent entity tag and one or more update entries corresponding to the subsequent entity tag to the client.

Abstract: A system for managing failover in a server cluster. In response to detecting a failed server, subscription message processing of a failover server is stopped. A subscription queue of the failed server is opened. A marker message is published to all subscribers of a particular messaging topic. The marker message includes an identification of the failover server managing the subscription queue of the failed server. Messages within the subscription queue of the failed server are processed. In response to determining that a message in the subscription queue of the failed server is the marker message, the subscription queue of the failed server is closed. Then, the failover server resumes processing of its original subscription queue looking for the marker message, while processing yet unseen messages from the queue. Once the marker message is found in the original subscription queue, normal operation is resumed.

Abstract: A cache server receives a request from a client that includes a requesting entity tag. In turn, the cache server extracts a starting identifier and an ending identifier from the requesting entity tag. The starting identifier is associated with a starting entry and the ending identifier is associated with an ending entry. Next, the cache server determines whether a subsequent entity tag exists that includes a subsequent starting identifier that matches the requesting entity tag's ending identifier. When the cache server identifies a subsequent entity tag, the cache server sends the subsequent entity tag and one or more update entries corresponding to the subsequent entity tag to the client.

Abstract: In response to detecting a failed server, subscription message processing of a failover server is stopped. A subscription queue of the failed server is opened. A marker message is published to all subscribers of a particular messaging topic. The marker message includes an identification of the failover server managing the subscription queue of the failed server. Messages within the subscription queue of the failed server are processed. In response to determining that a message in the subscription queue of the failed server is the marker message, the subscription queue of the failed server is closed. Then, the failover server resumes processing of its original subscription queue looking for the marker message, while processing yet unseen messages from the queue. Once the marker message is found in the original subscription queue, normal operation is resumed.