Internet client-server multiplexer

• US 6,954,780 B2
• Filed: 06/07/2002
• Issued: 10/11/2005
• Est. Priority Date: 11/10/1998
• Status: Expired due to Term

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: NetScaler Inc. (Cloud Software Group)
• Inventors: Setia, Deepinder S., Soni, Ajay V., Susai, Michel K., Sinha, Rajiv
• Primary Examiner(s): Cardone, Jason R.
• Assistant Examiner(s): LE, HIEU C
• Application Number:
  US10/163,342
• Publication Number:
  US 20020147822A1
• Time in Patent Office: 1,222 Days
• Field of Search: 709/201, 709/203, 709223-227, 709/229, 709/217, 709/245, 370/431, 711/124
• US Class Current: 709/203
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• 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

Abstract

An apparatus, method and computer program product for network client-server multiplexing. The apparatus is implemented within an interface unit connecting a plurality of servers to the Internet, which is connected to a plurality of clients. According to a “connection pooling” aspect of the invention, the interface unit opens and maintains connections with the servers and handles the opening and closing of connections with clients accessing the servers, thereby freeing the servers of the processing load incurred by opening and closing connections. According to a “connection distribution” aspect of the invention, the interface unit examines the path names within requests received from clients and selects the server hosting the requested information according to the path names.

Claims

1. A method comprising the steps of:

opening a connection to a server in response to a request from a first client and establishing sequence and acknowledgment numbers used to transfer data over said connection;

receiving from a second client a request to retrieve data using a network address and a path name, wherein the request from the second client includes sequence and acknowledgment parameters;

requesting said data from said server using said connection by modifying said sequence and acknowledgment parameters based on said established sequence and acknowledgment numbers used for said connection;

receiving data from said server;

modifying sequence and acknowledgment parameters in said data received from said server to produce modified sequence and acknowledgment parameters; and

sending said data to said second client with said modified sequence and acknowledgment parameters.

2. An apparatus comprising:

at least one of;

(a) means for selecting a server storing data as a function of predefined policies based on a path name, (b) means for selecting said server storing said data as a function of predetermined policies based on a load of said server, and (c) means for selecting said server storing said data as a function of predefined policies based on the state of said server;

means for identifying a previously-opened connection to said server established in response to a request from a first client, and identifying sequence and acknowledgment numbers to be used in said connection;

means for receiving from a second client a request to retrieve data using a network address and a path name, wherein the request from the second client includes a GET segment having sequence and acknowledgment parameters;

means for requesting said data from said server using said previously-opened connection by modifying said sequence and acknowledgment parameters in said GET segment to produce a modified GET segment based on said information identifying sequence and acknowledgment numbers already used, and sending said modified GET segment to said server;

means for receiving said data from said server; and

means for sending said data to said second client.

3. The apparatus of claim 2, wherein said means for sending said data to said second client comprises means for modifying sequence and acknowledgment parameters in said data upon receipt from said server to produce modified sequence and acknowledgment parameters, and sending said data to said second client with said modified sequence and acknowledgment parameters.

4. The apparatus of claim 2, wherein said information identifying sequence and acknowledgment numbers to be used in said connection comprise a starting sequence number and a starting acknowledge number respectively.

5. The apparatus of claim 2, wherein said means for receiving comprises:

means for receiving from said second client a request to open a connection to a host using said network address; and

means for receiving from said second client a request to retrieve data using said path name.

6. The apparatus of claim 2, further comprising:

means for receiving a further request to retrieve further data using said network address and a further path name;

means for selecting a further server as a function of said further path name; and

means for retrieving said further data from said further server.

7. The apparatus of claim 2, wherein said means for requesting said data from said server further comprises:

means for inserting a “

Connection;

Keep-Alive”

header into said modified GET segment;

means for subtracting from said acknowledgement parameters received from said server the number of bytes added by inserting said “

Connection;

Keep-Alive”

header into said modified GET segment; and

means for adding to said sequence number, prior to sending a packet to said server subsequent to said modified GET segment, the number of bytes added by inserting said “

Connection;

Keep Alive”

header into said modified GET segment.

8. The apparatus of claim 2, wherein said means for requesting said data from said server further comprises:

means for receiving a first RESP segment having further sequence and acknowledgment parameters;

means for modifying said further parameters to produce a modified RESP segment; and

means for sending said modified RESP segment to said client.

9. A method comprising the steps of:

opening a connection to a server in response to a request from a first client, said server selected as a function of predefined policies including at least one of a path name, a load of said server, and a state of said server;

identifying connection and sequence and acknowledgment numbers used in receiving data on said connection;

receiving from a second client a request to retrieve data, wherein the request from the second client includes sequence and acknowledgment parameters;

requesting said data from said server using said connection by modifying said sequence and acknowledgment parameters using said information identifying sequence and acknowledgment numbers used in said connection;

receiving data from said server; and

sending said data to said second client.

10. The method of claim 9, wherein said receiving step comprises the steps of:

receiving from said second client a request to open a connection to a host using a network address; and

receiving from said second client a request to retrieve data using a path name.

11. The method of claim 10, further comprising the steps of:

receiving a further request to retrieve further data using said network address and a further path name;

selecting a further server as a function of said further path name; and

retrieving said further data from said further server.

12. The method of claim 9, wherein:

said step of receiving a request to retrieve data comprises the step of receiving a first GET segment having sequence and acknowledgment parameters; and

said requesting step comprises the steps of

modifying said parameters to produce a modified GET segment, and

sending said modified GET segment to said server.

13. The method of claim 12, wherein said step of requesting said data from said server further comprises the steps of:

inserting a “

Connection;

Keep-Alive”

header into said modified GET segment;

subtracting from said acknowledgement parameters received from said server the number of bytes added by inserting said “

Connection;

Keep-Alive”

header into said modified GET segment; and

adding to said sequence number, prior to sending a packet to said server subsequent to said modified GET segment, the number of bytes added by inserting said “

Connection;

Keep Alive”

header into said modified GET segment.

14. The method of claim 12, further comprising the steps of:

receiving a first RESP segment having further sequence and acknowledgment parameters;

modifying said further parameters to produce a modified RESP segment; and

sending said modified RESP segment to said second client.

15. The method of claim 11 further comprising the steps of:

receiving a first RESP segment having further sequence and acknowledgment parameters;

modifying said further parameters to produce further modified parameters; and

sending a second RESP segment to said second client, said second RESP segment having said further modified parameters.

16. The method of claim 9, wherein:

said step of receiving a request to retrieve data comprises the step of receiving a first GET segment having sequence and acknowledgment parameters; and

said retrieving step comprises the steps of

modifying said parameters to produce modified parameters, and

sending a second GET segment to said server, said second GET segment having said modified parameters.

17. The method of claim 9 wherein said sequence and acknowledgment numbers used in receiving data on said connection are a starting sequence number and a starting acknowledgment number respectively.

18. The method of claim 9 wherein said step of sending said data to said second client comprises modifying sequence and acknowledgment parameters in said data upon receipt from said server to produce modified sequence and acknowledgment parameters, and sending said data to said second client with said modified sequence and acknowledgment parameters.