Splicing persistent connections
First Claim
Patent Images
1. A method of connecting a client to a server by a load balancer associated with a plurality of servers, comprising:
- establishing a first connection for transmission of packets between the load balancer and the client;
selecting a server to service the client; and
splicing the first connection with a second connection between the load balancer and the selected server, the second connection being established before the first connection.
3 Assignments
0 Petitions
Accused Products
Abstract
A method of connecting a client to a server by a load balancer associated with a plurality of servers. The method includes establishing a first connection for transmission of packets between the load balancer and the client, selecting a server to service the client, and splicing the first connection with a second connection between the load balancer and the selected server, the second connection being established before the first connection.
184 Citations
36 Claims
-
1. A method of connecting a client to a server by a load balancer associated with a plurality of servers, comprising:
-
establishing a first connection for transmission of packets between the load balancer and the client;
selecting a server to service the client; and
splicing the first connection with a second connection between the load balancer and the selected server, the second connection being established before the first connection. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A method of operating a load balancer associated with a plurality of servers, comprising:
-
establishing one or more connections with at least one of the plurality of servers;
splicing one or more of the established connections to client connections responsive to requests of clients to connect to one or more of the servers; and
monitoring the number of connections between the load balancer and the at least one of the plurality of servers, such that at least one of the connections leading to one or more of the servers is not spliced to connections with clients, when the total number of connections handled by each of the servers is below a respective predetermined maximal number of connections allowed by the server. - View Dependent Claims (21, 22, 23, 25, 26, 27, 28, 30, 31, 32)
-
-
24. A method of transmitting packets from a load balancer to a server, comprising:
-
establishing a TCP connection for transmission of packets between a load balancer and a server; and
transmitting packets received by the load balancer from a plurality of different clients, to the server, on the same TCP connection.
-
-
29. A method of connecting a client to a server by a load balancer associated with a plurality of servers, comprising:
-
establishing a first TCP connection between the load balancer and the client;
receiving a plurality of HTTP requests on the first connection;
selecting a server to service each of the HTTP requests, at least partially responsive to a content of the requests;
forwarding the requests to the selected respective servers, the selected servers including at least two servers;
receiving responses to the forwarded requests from the respective servers; and
forwarding the received responses to the client without storing the responses, for repeated use, by the load balancer.
-
-
33. A method of connecting a client to a server by a load balancer associated with a plurality of servers, comprising:
-
establishing a first TCP connection between the load balancer and the client;
splicing the first connection to a second connection between the load balancer and a server;
transmitting a plurality of packets on the spliced first and second connections; and
examining the application level contents of the plurality of packets transmitted on the connections to determine when to disconnect the splicing. - View Dependent Claims (34, 35, 36)
-
Specification