HTTP multiplexor/demultiplexor

• US 20020052931A1
• Filed: 10/10/2001
• Published: 05/02/2002
• Est. Priority Date: 10/10/2000
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Peiffer, Christopher, LʼHeureux, Israel
• Granted Patent: US 7,231,446 B2
• Time in Patent Office: Days
• US Class Current: 709/218
• 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/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/165 Combined use of TCP and UDP protocols; selection criteria therefor
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 370/916 Multiplexer/demultiplexer

Abstract

A computer networking system, method and device for multiplexing HTTP requests and demultiplexing HTTP responses. The method may include receiving HTTP requests from a plurality of clients and routing those requests to a socket on a server system. The method may also include receiving HTTP responses from the server system and selectively routing those responses to the corresponding clients.

Claims

1. A computer networking device for use on a computer network connecting a plurality of clients with a server system, the clients and server system being configured to communicate using Hypertext Transfer Protocol (HTTP), the computer networking device comprising an HTTP multiplexor/demultiplexor configured to receive HTTP requests from a plurality of the clients and to distribute those requests over an individual server TCP connection to a corresponding socket on the server system.

2. The computer networking device of claim 1, wherein the multiplexor/demultiplexor is further configured to receive HTTP responses from the server system over the individual server TCP connection and to route those responses to the clients via a plurality of client TCP connections.

3. A computer networking method for processing HTTP requests, comprising:

receiving HTTP requests from a plurality of originating clients; and

routing the HTTP requests to an individual socket on a server system via an individual server TCP connection.

4. The method of claim 3, wherein the requests are routed based on a parameter selected from the group consisting of least-lengthy response time, last-accessed socket, fewest number of unfulfilled requests, type of requested data, and size of requested data.

5. The method of claim 3, further comprising:

receiving HTTP responses from the server system via the individual server TCP connection; and

selectively routing the HTTP responses to the plurality of originating clients.

6. A computer networking method for data transfer between plural originating clients, a server system, and a networking device positioned on a computer network intermediate the clients and the server system, the method comprising:

at the networking device, listening for HTTP requests from the originating clients;

receiving HTTP requests from more than one of the originating clients;

multiplexing the received requests for delivery to the server system via an individual server TCP connection; and

sending the received requests via the individual server TCP connection to an optimal server socket.

7. The method of claim 6, wherein receiving HTTP requests from the originating clients occurs via client TCP connections.

8. The method of claim 7, wherein the client and server TCP connections are persistent.

9. The method of claim 6, wherein sending the received requests to an optimal server socket includes determining an optimal server socket.

10. The method of claim 9, wherein determining an optimal server socket includes determining a server socket with a least-lengthy response time.

11. The method of claim 9, wherein determining an optimal server socket includes determining a last-accessed server socket.

12. The method of claim 9, wherein determining an optimal server socket includes determining a server socket with the fewest number of unfulfilled requests.

13. The method of claim 6, further comprising listening for HTTP responses from the optimal server socket.

14. The method of claim 13, further comprising receiving HTTP responses from the optimal server socket.

15. The method of claim 14, further comprising demultiplexing the received HTTP responses to permit selective routing and transmission of the received responses to corresponding originating clients.

16. The method of claim 15, further comprising sending the HTTP responses to the corresponding originating clients.

19. The device of claim 18, wherein the computer networking device establishes TCP connections with the clients and with the socket on the server system.

20. The device of claim 19, wherein the TCP connections are persistent.

21. The device of claim 18, wherein the HTTP multiplexor/demultiplexor is further configured to determine an optimal server socket for receiving the HTTP requests.

17. A computer networking method for data transfer between plural originating clients, a server system and an intermediate networking device, wherein the originating clients and the server system are configured to communicate over a computer network via the intermediate networking device, the method comprising:

at the intermediate networking device, listening for HTTP requests from the originating clients;

receiving HTTP requests from more than one of the originating clients;

multiplexing the received requests;

determining an optimal server socket;

sending the received requests as a multiplexed transmission to the optimal server socket via an individual TCP connection;

listening for HTTP responses from the server system;

receiving HTTP responses from the server system;

demultiplexing the HTTP responses received from the server system to permit selective routing and transmission to corresponding originating clients; and

sending the received HTTP responses to the corresponding originating clients.

18. A computer networking device for use on a computer network to improve data transfer, the computer networking device being positioned intermediate plural clients and a server system, the clients and server system being configured to communicate via the computer network using HTTP communication protocol, the computer networking device comprising an HTTP multiplexor/demultiplexor configured to receive HTTP requests from the clients and to send the HTTP requests to a socket on the server system via multiplexed transmission, the computer networking device being further configured to receive HTTP responses from the server system and route the received HTTP responses to a corresponding one of the clients.

22. A computer networking system for use with a computer network, the system comprising:

a server system;

plural clients configured to connect to the server system via the computer network; and

a computer networking device positioned intermediate the server system and the clients on the computer network;

wherein the computer networking device is configured to receive HTTP requests from the clients and to distribute those requests via multiplexed transmission over an individual TCP connection to a server socket on the server system.

23. The computer networking system of claim 22, wherein the computer networking device is further configured to receive HTTP responses from the server system, demultiplex the responses, and route the demultiplexed responses to corresponding clients via a plurality of client TCP connections.

25. The device of claim 24, wherein the device is further configured to receive an HTTP response from the optimal server socket and to send the HTTP response to the client.

24. A computer networking device for improving data transfer via a computer network, the device being configured to receive HTTP requests from a client, determine an optimal server socket for each HTTP request, and to send each HTTP request to the determined optimal server socket for the request.