Apparatus, method and computer program product for efficiently pooling connections between clients and servers

• US 9,148,493 B2
• Filed: 12/16/2013
• Issued: 09/29/2015
• Est. Priority Date: 10/18/2000
• Status: Expired due to Fees

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Susai, Michel K., Sinha, Rajiv, Shetty, Anil
• Primary Examiner(s): Hussain, Tauqir
• Application Number:
  US14/107,971
• Publication Number:
  US 20140108513A1
• Time in Patent Office: 652 Days
• Field of Search: 709/203
• US Class Current: 1/1
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An apparatus, method and computer program product for efficiently pooling network client-server connections. The apparatus is implemented within an interface unit connecting a plurality of servers to the Internet, which is in turn connected to a plurality of clients. The method includes the steps of opening a connection between a first client and the interface unit; determining whether a connection between the interface unit and a server is finished being utilized by the first client; opening a connection between a second client and the interface unit; if no free connection is open between the interface unit and the server, then allowing the second client to access information on the server via the same connection utilized by the first client without waiting for the first client to initiate closing the connection; and delinking the connections between the first and second clients and the interface unit while keeping open the connection between the interface unit and the server.

Claims

1. A method comprising:

(a) establishing, by a device, a pool of one or more transport layer connections between the device and a server;

(b) forwarding, by the device, a first request of a first client to the server received via a first connection between the first client and the device over a second transport layer connection from the pool of one or more transport layer connections between the device and the server;

(c) determining, by the device while the device maintains open the transport layer connection of the pool of one or more transport layer connections between the device and the server, that the second transport layer connection is available for forwarding a second request of a second client via a third transport layer connection between the second client and the device to the server based on the server completing communicating a response to the first request of the first client via the second transport layer connection;

(d) forwarding, by the device responsive to the determination, the second request of the second client over the transport layer connection to the server prior to receiving a close command from the first client via the first transport layer connection between the first client and the device.

2. The method of claim 1, further comprising maintaining, by the device, the pool of one or more transport layer connections with the server open while closing one or more transport layers connections between the device and one or more clients accessing the server via the pool of one or more transport layer connections.

3. The method of claim 2, further comprising receiving, by the device while maintaining the pool of one or more transport layer connections with the server open, one or more close commands to close the one or more transport layer connections with the one or more clients.

4. The method of claim 1, wherein step (a) further comprises establishing, by the device, a second pool of one or more transport layer connections between the device and a second server.

5. The method of claim 4, further comprising forwarding, by the device, requests of different clients to the second server via the one or more transport layer connections of the second pool while forwarding requests of different clients to the server via the pool of one more transport layer connections.

6. The method of claim 1, wherein step (b) further comprises forwarding, by the device while maintaining the second transport layer connection open, the first request over the second transport layer connection after the device receives a response from another request of another client.

7. The method of claim 1, wherein step (c) further comprises determining, by the device, via a content length parameter identified in the response that a last byte of the application data has been communicated from the server for the request.

8. The method of claim 1, wherein step (c) further comprises determining, by the device, via a chunk-size field identified in the response that a last byte of the application data has been communicated from the server for the request.

17. The method of claim 1, further comprising, subsequent to step (d), forwarding, by the device, a second request of the first client to the server over the second transport layer connection from the pool of one or more transport layer connections.

18. The method of claim 1, wherein step (d) comprises forwarding, by the device, a second request of the second client over the second transport layer connection prior to receiving a FIN or an RST command from the first client.

9. A system comprising:

a device configured to establish a pool of one or more transport layer connections between the device and a server and forward a first request of a first client to the server received via a first transport layer connection between the first client and the device over a second transport layer connection from the pool of one or more transport layer connections;

wherein the device is configured to

determine, while the device maintains open the transport layer connection of the pool of one or more transport layer connections between the device and the server, that the second transport layer connection is available for forwarding a second request of a second client received via a third transport layer connection between the second client and the device to the server based on the server completing communicating a response to the first request of the first client via the second transport layer connection and responsive to the determination forward the second request of the second client over the second transport layer connection to the server,

forward the second request of the second client over the transport layer connection prior to receiving a close command from the first client via the first connection between the first client and the device, and

subsequently receive the close command from the first client via the first transport layer connection between the first client and the device to close the first transport layer connection between the first client and the device.

10. The system of claim 9, wherein the device is further configured to maintain the pool of one or more transport layer connections with the server open while closing one or more transport layers connections between the device and one or more clients accessing the server via the pool of one or more transport layer connections.

11. The system of claim 10, wherein the device is further configured to receive, while maintaining the pool of one or more transport layer connections with the server open, one or more close commands to close the one or more transport layer connections with the one or more clients.

12. The system of claim 9, wherein the device is further configured to establish a second pool of one or more transport layer connections between the device and a second server.

13. The system of claim 12, wherein the device is further configured to forward requests of different clients to the second server via the one or more transport layer connections of the second pool while forwarding requests of different clients to the server via the pool of one more transport layer connections.

14. The system of claim 9, wherein the device is further configured to forward, while maintaining the second transport layer connection open, the first request over the second transport layer connection after the device receives a response from another request of another client.

15. The system of claim 9, wherein the device is further configured to determine, via a content length parameter identified in the response that a last byte of the application data has been communicated from the server for the request.

16. The system of claim 9, wherein the device is further configured to determine via a chunk-size field identified in the response that a last byte of the application data has been communicated from the server for the request.

19. The system of claim 9, wherein the device is further configured to forward a second request of the first client to the server over the second transport layer connection from the pool of one or more transport layer connections.

20. The method of claim 9, wherein the device is further configured to forward a second request of the second client over the second transport layer connection prior to receiving a FIN or an RST command from the first client.