DYNAMIC CLIENT REGISTRATION FOR SERVER PUSH EVENTS IN LONG POLLING SCENARIOS

• US 20140012997A1
• Filed: 07/05/2012
• Published: 01/09/2014
• Est. Priority Date: 07/05/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Erbe, Lars
• Granted Patent: US 9,088,622 B2
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

The disclosure generally describes computer-implemented methods, software, and systems for modeling and deploying decision services. One computer-implemented method includes establishing a push-channel session uniquely associated with a client, wherein the push channel session communicates with the client using a single push channel. The computer-implemented method further includes registering the established push-channel session with a messaging channel runtime creating a client-specific messaging channel and registering a backend application with the push-channel-session-associated single push channel using a push channel registration session. The method further includes, responsive to an application message received from an application session associated with the backend application using a client-specific application channel, dispatching the received application message to the push-channel session from the messaging channel runtime using the client-specific messaging channel. The method includes communicating the dispatched application message to the client using the single push channel.

Claims

1. A computer-implemented method, comprising:

establishing a push-channel session uniquely associated with a client, wherein the push channel session communicates with the client using a single push channel;

registering the established push-channel session with a messaging channel runtime creating a client-specific messaging channel;

registering a backend application with the push-channel-session-associated single push channel using a push channel registration session;

responsive to an application message received from an application session associated with the backend application using a client-specific application channel, dispatching the received application message to the push-channel session from the messaging channel runtime using the client-specific messaging channel; and

communicating the dispatched application message to the client using the single push channel.

2. The computer-implemented method of claim 1, wherein the single push channel is implemented using at least one of long polling or web sockets.

3. The computer-implemented method of claim 1, wherein the registration using the push channel registration session is performed on the messaging channel runtime and the push session.

4. The computer-implemented method of claim 3, wherein, prior to the registration, the push channel registration session receives at least one of a registration or a de-registration request for the backend application.

5. The computer-implemented method of claim 1, further comprising, prior to receiving the application message associated with the application session, registering the client-specific application channel between the application session and the messaging channel runtime.

6. The computer-implemented method of claim 5, wherein the messaging channel runtime dispatches the received application message using the client-specific messaging channel corresponding to the client associated with the application channel.

7. The computer-implemented method of claim 1 wherein the communicated application message is dispatched by a client push dispatcher to the client application associated with the application session.

8. A computer program product, tangibly embodied in a machine-readable storage device, the computer program product being operable to cause data processing apparatus to perform operations comprising:

establishing a push-channel session uniquely associated with a client, wherein the push channel session communicates with the client using a single push channel;

registering the established push-channel session with a messaging channel runtime creating a client-specific messaging channel;

registering a backend application with the push-channel-session-associated single push channel using a push channel registration session;

responsive to an application message received from an application session associated with the backend application using a client-specific application channel, dispatching the received application message to the push-channel session from the messaging channel runtime using the client-specific messaging channel; and

communicating the dispatched application message to the client using the single push channel.

9. The computer program product of claim 8, wherein the single push channel is implemented using at least one of long polling or web sockets.

10. The computer program product of claim 8, wherein the registration using the push channel registration session is performed on the messaging channel runtime and the push session.

11. The computer program product of claim 10, wherein, prior to the registration, the push channel registration session receives at least one of a registration or a de-registration request for the backend application.

12. The computer program product of claim 8, further comprising, prior to receiving the application message associated with the application session, registering the client-specific application channel between the application session and the messaging channel runtime.

13. The computer program product of claim 12, wherein the messaging channel runtime dispatches the received application message using the client-specific messaging channel corresponding to the client associated with the application channel.

14. The computer program product of claim 8 wherein the communicated application message is dispatched by a client push dispatcher to the client application associated with the application session.

15. A system, comprising:

memory operable to store at least one decision service; and

at least one hardware processor interoperably coupled to the memory and configured to perform operations comprising;

establishing a push-channel session uniquely associated with a client, wherein the push channel session communicates with the client using a single push channel;

registering the established push-channel session with a messaging channel runtime creating a client-specific messaging channel;

registering a backend application with the push-channel-session-associated single push channel using a push channel registration session;

responsive to an application message received from an application session associated with the backend application using a client-specific application channel, dispatching the received application message to the push-channel session from the messaging channel runtime using the client-specific messaging channel; and

communicating the dispatched application message to the client using the single push channel.

16. The system of claim 15, wherein the single push channel is implemented using at least one of long polling or web sockets.

17. The system of claim 15, wherein the registration using the push channel registration session is performed on the messaging channel runtime and the push session.

18. The system of claim 17, wherein, prior to the registration, the push channel registration session receives at least one of a registration or a de-registration request for the backend application.

19. The system of claim 15, wherein the at least one hardware processor is further configured to perform operations comprising:

prior to receiving the application message associated with the application session, registering the client-specific application channel between the application session and the messaging channel runtime.

20. The system of claim 19, wherein the messaging channel runtime dispatches the received application message using the client-specific messaging channel corresponding to the client associated with the application channel.