NOTIFICATION MODEL OVER A SERVER-TO-SERVER CONNECTION POOL

• US 20100217872A1
• Filed: 02/26/2009
• Published: 08/26/2010
• Est. Priority Date: 02/26/2009
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Martchenko, Serguei V.
• Granted Patent: US 8,886,787 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/147 Signalling methods or messages providing extensions to protocols defined by standardisation
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A server-to-server notification model that employs a connection pool such that an asynchronous request issued from the pool can access any session of the remote server for pending notifications on all of the sessions. Only one asynchronous request (or call) is issued to the remote server for all sessions in the connection pool, and the call is completed if any notifications to any participating sessions occur on the remote server. When the asynchronous request completes, the returned data provides a set of the sessions that have pending notifications.

Claims

1. A computer-implemented notification system, comprising:

a request component of a local server for processing a request of a connection pool for one or more change notifications in sessions of a remote server; and

a return component for receiving session data related to the sessions in the remote server having pending notifications.

2. The system of claim 1, wherein the session data is a set of all sessions having pending change notifications.

3. The system of claim 2, wherein the return component completes the request in response to receiving the session data.

4. The system of claim 1, wherein the request maps to all sessions associated with the connection pool.

5. The system of claim 1, wherein the request is a remote procedure call (RPC) issued asynchronously by the local server, which is a middle tier server, to the remote server, which is a backend server, for the one or more notifications.

6. The system of claim 5, wherein the middle tier server and the backend server are messaging servers.

7. The system of claim 1, wherein the request uses a handle of an RPC connection, the handle is released back to the connection pool upon completion of the request.

8. The system of claim 1, wherein the request is queued, and then completed in response to a notification that occurs after the request is sent.

9. The system of claim 1, wherein the request is queued, and then immediately completed in response to a notification that occurred before the request was sent.

10. A computer-implemented notification system, comprising:

a request component of a local server for issuing a call to a remote server for sessions in a connection pool established between the local server and the remote server; and

a return component for completing the call if at least one notification is pending in the sessions.

11. The system of claim 10, wherein the call is an RPC of a connection in the connection pool, the call issued asynchronously to the remote server utilizing a connection from the pool and the connection is released back to the connection pool when the call completed.

12. The system of claim 10, wherein the completion of the RPC call returns a subset of all sessions in the connection pool.

13. The system of claim 10, wherein the call is queued, and then completed in response to a notification that occurs in one of the sessions.

14. The system of claim 10, wherein the call is issued and immediately completed in response to notifications that occurred before the call was issued.

15. A computer-implemented method of notification, comprising:

establishing a connection pool of connections between a local server and session objects of a remote server;

issuing a request from the local server to the remote server for all session objects in the connection pool; and

responding to the request if a notification exists for one or more of the session objects of the remote server.

16. The method of claim 15, further comprising responding with a list of all session objects having pending notifications.

17. The method of claim 15, wherein the request is an RPC call issued asynchronously by the local server, which is a middle tier messaging server, to the remote server, which is a backend messaging server.

18. The method of claim 15, further comprising:

queuing the request at the remote server until a notification occurs; and

responding to the request with a set of session objects having pending notifications.

19. The method of claim 15, further comprising responding immediately to the request with a set of session objects having pending notifications if the notification already exists for one of the session objects.

20. The method of claim 15, further comprising releasing the connection back to the connection pool after the request has been completed.