Client-side fault tolerance in a publish-subscribe system
First Claim
Patent Images
1. A method for client-side fault-tolerance in a publish-subscribe system, the method comprising:
- receiving, on a channel, a message from a server;
determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data;
determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message;
sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message;
clearing, responsive to sending the refresh message, the last known content signature from the previous message;
receiving, responsive to the refresh message, a response message;
setting the last known content signature with a content signature contained in the response message;
activating a timeout timer upon receiving the response message;
receiving, prior to the timeout timer expiring, a next message subsequent to the response message;
determining that the next message carries a second heartbeat data;
determining that a second content signature contained in the next message matches the last known content signature saved from the response message;
resetting and reactivating the timeout timer upon receiving the next message; and
monitoring the channel for a content update from the server.
1 Assignment
0 Petitions
Accused Products
Abstract
To provide client-side fault-tolerance in a publish-subscribe system, a message is received on a channel from a server. At a function executing using a processor and a memory, a determination is made whether the message contains a heartbeat data. When the message contains the heartbeat data, a determination is made whether a content signature contained in the message matches a last known content signature saved from a previous message. When the content signature contained in the message does not match the last known content signature saved from a previous message, a refresh message is sent to the channel.
-
Citations
17 Claims
-
1. A method for client-side fault-tolerance in a publish-subscribe system, the method comprising:
-
receiving, on a channel, a message from a server; determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data; determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message; sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message; clearing, responsive to sending the refresh message, the last known content signature from the previous message; receiving, responsive to the refresh message, a response message; setting the last known content signature with a content signature contained in the response message; activating a timeout timer upon receiving the response message; receiving, prior to the timeout timer expiring, a next message subsequent to the response message; determining that the next message carries a second heartbeat data; determining that a second content signature contained in the next message matches the last known content signature saved from the response message; resetting and reactivating the timeout timer upon receiving the next message; and monitoring the channel for a content update from the server. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A computer usable program product comprising a computer readable storage device including computer usable code for client-side fault-tolerance in a publish-subscribe system, the computer usable code comprising:
-
computer usable code for receiving, on a channel, a message from a server; computer usable code for determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data; computer usable code for determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message; computer usable code for sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message; computer usable code for clearing, responsive to sending the refresh message, the last known content signature from the previous message; computer usable code for receiving, responsive to the refresh message, a response message; computer usable code for setting the last known content signature with a content signature contained in the response message; computer usable code for activating a timeout timer upon receiving the response message; computer usable code for receiving, prior to the timeout timer expiring, a next message subsequent to the response message; computer usable code for determining that the next message carries a second heartbeat data; computer usable code for determining that a second content signature contained in the next message matches the last known content signature saved from the response message; computer usable code for resetting and reactivating the timeout timer upon receiving the next message; and computer usable code for monitoring the channel for a content update from the server. - View Dependent Claims (7, 8, 9, 10, 11, 12)
-
-
13. A data processing system for client-side fault-tolerance in a publish-subscribe system, the data processing system comprising:
-
a storage device, wherein the storage device stores computer usable program code; and a processor, wherein the processor executes the computer usable program code, and wherein the computer usable program code comprises; computer usable code for receiving, on a channel, a message from a server; computer usable code for determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data; computer usable code for determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message; computer usable code for sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message; computer usable code for clearing, responsive to sending the refresh message, the last known content signature from the previous message; computer usable code for receiving, responsive to the refresh message, a response message; computer usable code for setting the last known content signature with a content signature contained in the response message; computer usable code for activating a timeout timer upon receiving the response message; computer usable code for receiving, prior to the timeout timer expiring, a next message subsequent to the response message; computer usable code for determining that the next message carries a second heartbeat data; computer usable code for determining that a second content signature contained in the next message matches the last known content signature saved from the response message; computer usable code for resetting and reactivating the timeout timer upon receiving the next message; and computer usable code for monitoring the channel for a content update from the server. - View Dependent Claims (14, 15, 16, 17)
-
Specification