Method and apparatus for optimization of remote procedure call communications

• US 7,853,962 B1
• Filed: 05/31/2005
• Issued: 12/14/2010
• Est. Priority Date: 05/31/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Glixman, Shahar, Vasetsky, Leonid, Romano, Ophir, Ben-Shaul, Israel Zvi
• Primary Examiner(s): Nguyen; Van H
• Application Number:
  US11/141,761
• Time in Patent Office: 2,023 Days
• Field of Search: 719/310, 719/315, 719/316, 719/330, 719/331, 719/332, 709/203, 709/217, 709/224
• US Class Current: 719/330
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A method and apparatus is disclosed for optimization of Remote Procedure Call (RPC) communications. A first RPC request to open a first transport connection is sent to a RPC service. A first RPC response is received from the RPC service. The first RPC response includes first information which indicates that first transport connection is open. The first information is stored in a cache. In response to a second RPC request to close the first transport connection, the closing of the first transport connection is delayed.

Claims

1. A method for optimization of Remote Procedure Call (RPC) communications, comprising the computer-implemented steps of:

sending a first RPC request to open a first transport connection to a RPC service;

receiving a first RPC response from the RPC service, wherein the first RPC response includes first information which indicates that the first transport connection to the RPC service is open;

wherein the RPC service is configured to execute remote procedure calls sent over the first transport connection;

storing the first information in a cache;

in response to a second RPC request to close the first transport connection, delaying the closing of the first transport connection to the RPC service;

receiving a third RPC request to open a new transport connection to the RPC service;

determining whether there is any open transport connection to the RPC service; and

if it is determined that the first transport connection is still open, then performing the steps of;

retrieving the first information from the cache; and

responding to the third RPC request by creating and sending a second RPC response that includes the first information;

wherein the method is performed by one or more computer systems.

2. The method as recited in claim 1, further comprising:

creating a third RPC response which indicates that the first transport connection is closed even though the closing of the first transport connection has been delayed; and

responding to the second RPC request to close the first transport connection by sending the third RPC response.

3. The method as recited in claim 1, wherein:

the closing of the first transport connection is delayed for a predetermined interval of time; and

the method further comprises closing the first transport connection after the predetermined interval of time expires.

4. The method as recited in claim 3, wherein the predetermined interval of time represents an interval of time during which no RPC operations were sent to the RPC service over the first transport connection.

5. The method as recited in claim 1, wherein the first transport connection is established according to any one of a Server Message Block (SMB) protocol, Transmission Control Protocol (TCP), and HyperText Transfer Protocol (HTTP).

6. The method as recited in claim 1, wherein the steps are performed in a packet-switched network in any of a router, a switch, and a server.

7. A method for optimization of Remote Procedure Call (RPC) communications, comprising the computer-implemented steps of:

receiving from a client a first RPC request to open a first transport connection to a particular RPC service of one or more RPC services, wherein access to the one or more RPC services is managed by a remote server that is communicatively connected over a slow communication link;

sending the first RPC request to the remote server;

receiving a first RPC response from the remote server, wherein the first RPC response includes first information which identifies the first transport connection and indicates that the first transport connection to the particular RPC service is open;

wherein the particular RPC service is configured to execute remote procedure calls sent over the first transport connection;

storing the first information in a cache;

in response to receiving from the client a second RPC request to close the first transport connection to the particular RPC service, delaying the closing of the first transport connection to the particular RPC service;

receiving from the client a third RPC request to open a new transport connection to the particular RPC service;

determining whether there is any open transport connection to the particular RPC service by examining the contents of the cache; and

if it is determined that the first transport connection is still open, then performing the steps of;

retrieving the first information from the cache; and

responding to the third RPC request by performing the steps of;

creating a second RPC response that includes the first information; and

sending the second RPC response to the client;

wherein the method is performed by one or more computer systems.

8. The method as recited in claim 7, further comprising:

creating a third RPC response which indicates that the first transport connection to the particular RPC service is closed even though the closing of the first transport connection has been delayed; and

responding to the second RPC request to close the first transport connection by sending the third RPC response to the client.

9. The method as recited in claim 7, further comprising:

before receiving from the client the second RPC request to close the first transport connection to the particular RPC service, performing the steps of;

receiving, from the client, one or more RPC operations for execution by the particular RPC service;

sending the one or more RPC operations to the remote server over the first transport connection;

receiving from the remote server one or more RPC responses which indicate that the one or more RPC operations have been executed by the particular RPC service; and

storing in the cache the one or more RPC responses; and

after responding to the third RPC request, performing the steps of;

receiving, from the client, a particular RPC operation of the one or more RPC operations for execution by the particular RPC service;

retrieving from the cache a particular RPC response of the one or more RPC responses, wherein the particular RPC response was previously received from the remote server in response to executing the particular RPC operation by the particular RPC service; and

responding to the particular RPC request by sending the particular RPC response to the client.

10. The method as recited in claim 9, wherein:

the first transport connection is any one of a pipe established according to a Server Message Block (SMB) protocol and a socket established according to a Transmission Control Protocol (TCP); and

the particular RPC operation is a RPC bind operation that binds the client to the particular RPC service through the first transport connection.

11. The method as recited in claim 7, further comprising:

closing the first transport connection to the particular RPC service after the expiration of a predetermined interval of time; and

removing the first information from the cache.

12. The method as recited in claim 7, wherein the first transport connection is established according to any one of a Server Message Block (SMB) protocol, Transmission Control Protocol (TCP), and HyperText Transfer Protocol (HTTP).

13. The method as recited in claim 7, wherein:

the first RPC request to open the first transport connection to the particular RPC service is sent from a particular user of one or more users associated with the client; and

storing the first information in the cache further comprises storing second information that is associated with the first information, wherein the second information identifies the particular user of the client.

14. The method as recited in claim 7, wherein:

the slow communication link is established between a local server and the remote server, wherein the slow communication link is any one of a dial-up connection, a Wide Area Network (WAN) connection, a Digital Subscriber Line (DSL) connection, and an Integrated Services Digital Network (ISDN) connection;

the client is communicatively connected to the local server over a first connection; and

the one or more RPC services are communicatively connected to the remote server over a second connection.

15. An apparatus for optimization of Remote Procedure Call (RPC) communications, comprising:

one or more processors;

means for sending a first RPC request to open a first transport connection to a RPC service;

means for receiving a first RPC response from the RPC service, wherein the first RPC response includes first information which indicates that the first transport connection to the RPC service is open;

wherein the RPC service is configured to execute remote procedure calls sent over the first transport connection;

means for storing the first information in a cache;

means for delaying the closing of the first transport connection in response to a second RPC request to close the first transport connection to the RPC service;

means for receiving a third RPC request to open a new transport connection to the RPC service;

means for determining whether there is any open transport connection to the RPC service;

means for retrieving the first information from the cache if it is determined that the first transport connection is still open; and

means for responding to the third RPC request, if it is determined that the first transport connection is still open, by creating and sending a second RPC response that includes the first information.

16. The apparatus of claim 15, further comprising:

means for creating a third RPC response which indicates that the first transport connection is closed even though the closing of the first transport connection has been delayed; and

means for responding to the second RPC request to close the first transport connection by sending the third RPC response.

17. The apparatus of claim 15, wherein:

the closing of the first transport connection is delayed for a predetermined interval of time; and

the apparatus further comprises means for closing the first transport connection after the predetermined interval of time expires.

18. The apparatus of claim 17, wherein the predetermined interval of time represents an interval of time during which no RPC operations were sent to the RPC service over the first transport connection.

19. The apparatus of claim 15, wherein the first transport connection is established according to any one of a Server Message Block (SMB) protocol, Transmission Control Protocol (TCP), and HyperText Transfer Protocol (HTTP).

20. The apparatus of claim 15, wherein the apparatus is any of a router, a switch, and a server.

21. An apparatus for optimization of Remote Procedure Call (RPC) communications, comprising:

one or more processors;

one or more stored sequences of instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of;

receiving from a client a first RPC request to open a first transport connection to a particular RPC service of one or more RPC services, wherein access to the one or more RPC services is managed by a remote server that is communicatively connected to the apparatus over a slow communication link;

sending the first RPC request to the remote server;

receiving a first RPC response from the remote server, wherein the first RPC response includes first information which identifies the first transport connection and indicates that the first transport connection to the particular RPC service is open;

wherein the particular RPC service is configured to execute remote procedure calls sent over the first transport connection;

storing the first information in a cache;

in response to receiving from the client a second RPC request to close the first transport connection to the particular RPC service, delaying the closing of the first transport connection to the particular RPC service;

receiving from the client a third RPC request to open a new transport connection to the particular RPC service;

determining whether there is any open transport connection to the particular RPC service by examining the contents of the cache; and

if it is determined that the first transport connection is still open, then performing the steps of;

retrieving the first information from the cache; and

responding to the third RPC request by performing the steps of;

creating a second RPC response that includes the first information; and

sending the second RPC response to the client.

22. The apparatus of claim 21, wherein the instructions further cause the one or more processors to perform the steps of:

creating a third RPC response which indicates that the first transport connection to the particular RPC service is closed even though the closing of the first transport connection has been delayed; and

responding to the second RPC request to close the first transport connection by sending the third RPC response to the client.

23. The apparatus of claim 21, wherein the instructions further cause the one or more processors to perform the steps of:

before receiving from the client the second RPC request to close the first transport connection to the particular RPC service, performing the steps of;

receiving, from the client, one or more RPC operations for execution by the particular RPC service;

sending the one or more RPC operations to the remote server over the first transport connection;

receiving from the remote server one or more RPC responses which indicate that the one or more RPC operations have been executed by the particular RPC service; and

storing in the cache the one or more RPC responses; and

after responding to the third RPC request, performing the steps of;

receiving, from the client, a particular RPC operation of the one or more RPC operations for execution by the particular RPC service;

retrieving from the cache a particular RPC response of the one or more RPC responses, wherein the particular RPC response was previously received from the remote server in response to executing the particular RPC operation by the particular RPC service; and

responding to the particular RPC request by sending the particular RPC response to the client.

24. The apparatus of claim 23, wherein:

the first transport connection is any one of a pipe established according to a Server Message Block (SMB) protocol and a socket established according to a Transmission Control Protocol (TCP); and

the particular RPC operation is a RPC bind operation that binds the client to the particular RPC service through the first transport connection.

25. The apparatus of claim 21, wherein the instructions further cause the one or more processors to perform the steps of:

closing the first transport connection to the particular RPC service after the expiration of a predetermined interval of time; and

removing the first information from the cache.

26. The apparatus of claim 21, wherein the first transport connection is established according to any one of a Server Message Block (SMB) protocol, Transmission Control Protocol (TCP), and HyperText Transfer Protocol (HTTP).

27. The apparatus of claim 21, wherein:

the first RPC request to open the first transport connection to the particular RPC service is sent from a particular user of one or more users associated with the client; and

storing the first information in the cache further comprises storing second information that is associated with the first information, wherein the second information identifies the particular user of the client.

28. The apparatus of claim 21, wherein:

the slow communication link between the apparatus and the remote server is any one of a dial-up connection, a Wide Area Network (WAN) connection, a Digital Subscriber Line (DSL) connection, and an Integrated Services Digital Network (ISDN) connection;

the client is communicatively connected to the apparatus over a first Local Area Network (LAN); and

the one or more RPC services are communicatively connected to the remote server over a second LAN.

29. A non-transitory computer-readable volatile or non-volatile medium storing one or more sequences of instructions for optimization of Remote Procedure Call (RPC) communications, which instructions, when executed by one or more processors, cause the one or more processors to perform steps comprising:

sending a first RPC request to open a first transport connection to a RPC service;

receiving a first RPC response from the RPC service, wherein the first RPC response includes first information which indicates that the first transport connection to the RPC service is open;

wherein the RPC service is configured to execute remote procedure calls sent over the first transport connection;

storing the first information in a cache;

in response to a second RPC request to close the first transport connection, delaying the closing of the first transport connection to the RPC service;

receiving a third RPC request to open a new transport connection to the RPC service;

determining whether there is any open transport connection to the RPC service; and

if it is determined that the first transport connection is still open, then performing the steps of;

retrieving the first information from the cache; and

responding to the third RPC request by creating and sending a second RPC response that includes the first information.

30. The non-transitory computer-readable volatile or non-volatile medium of claim 29, wherein the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of:

creating a third RPC response which indicates that the first transport connection is closed even though the closing of the first transport connection has been delayed; and

responding to the second RPC request to close the first transport connection by sending the third RPC response.

31. The non-transitory computer-readable volatile or non-volatile medium of claim 29, wherein:

the closing of the first transport connection is delayed for a predetermined interval of time; and

the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the step of closing the first transport connection after the predetermined interval of time expires.

32. A non-transitory computer-readable volatile or non-volatile medium storing one or more sequences of instructions for optimization of Remote Procedure Call (RPC) communications, which instructions, when executed by one or more processors, cause the one or more processors to perform steps comprising:

receiving from a client a first RPC request to open a first transport connection to a particular RPC service of one or more RPC services, wherein access to the one or more RPC services is managed by a remote server that is communicatively connected by a slow communication link;

sending the first RPC request to the remote server;

receiving a first RPC response from the remote server, wherein the first RPC response includes first information which identifies the first transport connection and indicates that the first transport connection to the particular RPC service is open;

wherein the particular RPC service is configured to execute remote procedure calls sent over the first transport connection;

storing the first information in a cache;

in response to receiving from the client a second RPC request to close the first transport connection to the particular RPC service, delaying the closing of the first transport connection to the particular RPC service;

receiving from the client a third RPC request to open a new transport connection to the particular RPC service;

determining whether there is any open transport connection to the particular RPC service by examining the contents of the cache; and

if it is determined that the first transport connection is still open, then performing the steps of;

retrieving the first information from the cache; and

responding to the third RPC request by performing the steps of;

creating a second RPC response that includes the first information; and

sending the second RPC response to the client.

33. The non-transitory computer-readable volatile or non-volatile medium of claim 32, wherein the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of:

creating a third RPC response which indicates that the first transport connection to the particular RPC service is closed even though the closing of the first transport connection has been delayed; and

responding to the second RPC request to close the first transport connection by sending the third RPC response to the client.

34. The non-transitory computer-readable volatile or non-volatile medium of claim 32, wherein the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of:

before receiving from the client the second RPC request to close the first transport connection to the particular RPC service, performing the steps of;

receiving, from the client, one or more RPC operations for execution by the particular RPC service;

sending the one or more RPC operations to the remote server over the first transport connection;

receiving from the remote server one or more RPC responses which indicate that the one or more RPC operations have been executed by the particular RPC service; and

storing in the cache the one or more RPC responses; and

after responding to the third RPC request, performing the steps of;

receiving, from the client, a particular RPC operation of the one or more RPC operations for execution by the particular RPC service;

retrieving from the cache a particular RPC response of the one or more RPC responses, wherein the particular RPC response was previously received from the remote server in response to executing the particular RPC operation by the particular RPC service; and

responding to the particular RPC request by sending the particular RPC response to the client.

35. The non-transitory computer-readable volatile or non-volatile medium of claim 32, wherein the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of:

closing the first transport connection to the particular RPC service after the expiration of a predetermined interval of time; and

removing the first information from the cache.

36. The non-transitory computer-readable volatile or non-volatile medium of claim 32, wherein:

the first RPC request to open the first transport connection to the particular RPC service is sent from a particular user of one or more users associated with the client; and

the instructions that cause the one or more processors to perform the step of storing the first information in the cache further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the step of storing second information that is associated with the first information, wherein the second information identifies the particular user of the client.