Resilient messaging infrastructure
First Claim
1. A system, comprising:
- a memory; and
a processor programmed to;
receive, at a first message resilience client device from a second message resilience client device, a message and a request to deliver the message to a client/server-based server application executed by a server device on behalf of a remote client/server-based client application executed by the second message resilience client device that originated the message;
determine whether a connection to the server device that executes the client/server-based server application is currently possible via at least one available connection;
store, in response to determining that the connection to the server device that executes the client/server-based server application is not currently possible via the at least one available connection, the message locally in the memory for one of later delivery to the client/server-based server application and propagation of the message to at least one other message resilience client device on behalf of the remote client/server-based client application executed by the second message resilience client device;
determine, in response to the first message resilience client device coming into proximity with at least one other message resilience client device, whether an alternative connection to any of the at least one other message resilience client device is available; and
propagate, to the at least one other message resilience client device to which the alternative connection is determined to be available, the message and the request to deliver the message to the client/server-based server application executed by the server device on behalf of the remote client/server-based client application executed by the second message resilience client device.
1 Assignment
0 Petitions
Accused Products
Abstract
A first message resilience client device receives from a second message resilience client device a message and a request to deliver the message to a client/server-based server application executed by a server device on behalf of a remote client/server-based client application executed by the second message resilience client device that originated the message. A determination is made as to whether a connection to the server device that executes the client/server-based server application is currently possible using at least one available connection. In response to determining that the connection to the server device that executes the client/server-based server application is not currently possible, the message is stored locally for one of later delivery to the client/server-based server application and propagation of the message to another message resilience client device on behalf of the remote client/server-based client application.
4 Citations
14 Claims
-
1. A system, comprising:
-
a memory; and a processor programmed to; receive, at a first message resilience client device from a second message resilience client device, a message and a request to deliver the message to a client/server-based server application executed by a server device on behalf of a remote client/server-based client application executed by the second message resilience client device that originated the message; determine whether a connection to the server device that executes the client/server-based server application is currently possible via at least one available connection; store, in response to determining that the connection to the server device that executes the client/server-based server application is not currently possible via the at least one available connection, the message locally in the memory for one of later delivery to the client/server-based server application and propagation of the message to at least one other message resilience client device on behalf of the remote client/server-based client application executed by the second message resilience client device; determine, in response to the first message resilience client device coming into proximity with at least one other message resilience client device, whether an alternative connection to any of the at least one other message resilience client device is available; and propagate, to the at least one other message resilience client device to which the alternative connection is determined to be available, the message and the request to deliver the message to the client/server-based server application executed by the server device on behalf of the remote client/server-based client application executed by the second message resilience client device. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer program product, comprising:
a computer readable storage medium having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to; receive, at a first message resilience client device from a second message resilience client device, a message and a request to deliver the message to a client/server-based server application executed by a server device on behalf of a remote client/server-based client application executed by the second message resilience client device that originated the message; determine whether a connection to the server device that executes the client/server-based server application is currently possible via at least one available connection; store, in response to determining that the connection to the server device that executes the client/server-based server application is not currently possible via the at least one available connection, the message locally for one of later delivery to the client/server-based server application and propagation of the message to at least one other message resilience client device on behalf of the remote client/server-based client application executed by the second message resilience client device determine, in response to the first message resilience client device coming into proximity with at least one other message resilience client device, whether an alternative connection to any of the at least one other message resilience client device is available; and propagate, to the at least one other message resilience client device to which the alternative connection is determined to be available, the message and the request to deliver the message to the client/server-based server application executed by the server device on behalf of the remote client/server-based client application executed by the second message resilience client device. - View Dependent Claims (9, 10, 11, 12, 13, 14)
Specification