System and method for managing client requests in client-server networks

• US 6,912,588 B1
• Filed: 04/02/1998
• Issued: 06/28/2005
• Est. Priority Date: 04/02/1998
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Schnetzler, Steven, Jardin, Cary A.
• Primary Examiner(s): Teska, Kevin J.
• Assistant Examiner(s): THOMSON, WILLIAM D
• Application Number:
  US09/054,304
• Time in Patent Office: 2,644 Days
• Field of Search: 709/202, 709/203, 709/217, 709/218, 709/245, 709/230, 709/219, 709/238, 709/239, 709/227, 709/226, 707/10
• US Class Current: 709/238
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A broker for the management of client requests issued by a client computer over a client-server network. Depending on its availability of resources, the broker determines whether to respond to the client request, or hand-off the client request to another server. The broker supports a virtual connection between the client and the other server, without interfering with communication protocols or disrupting client requests. The other server fulfills client requests by operating in place of the broker. The server terminates the virtual connection when all client requests have been completely fulfilled.

Claims

1. A method of managing a client request in a client-server network having a client, a first server, and a second server, the method comprising:

performing a handshake between the client and the first server;

determining whether to fulfill the client request by the first server;

selecting the second server, when the client request cannot be fulfilled by the first server;

performing a handshake between the first server and the second server;

forwarding the client request to the second server for execution, the forwarding being transparent to the client; and

responding to the client by a one-way direct data transmission from the second server to the client.

2. The method as claimed in claim 1, wherein determining whether to fulfill the client request includes determining if the first server is equipped with an appropriate resource.

3. The method as claimed in claim 1, wherein forwarding the client request to the second server includes writing the destination address of the second server in a packet received from the client.

4. The method as claimed in claim 3, wherein forwarding the client request to the second server includes transmitting the packet to the second server.

5. The method as claimed in claim 1, further comprising the step of sending an acknowledgment by the first server to the client after receiving an acknowledgment packet from the second server.

6. The method as claimed in claim 1, wherein responding to the client includes forwarding client data to the second server.

7. The method as claimed in claim 1, wherein responding to the client includes writing the source address of the first server in a response packet transmitted by the second server.

8. The method as claimed in claim 7, wherein responding to the client includes transmitting the response packet to the client.

9. A system for managing a client request in a client-server network, the system comprising:

a first server configured to perform a handshake with a client and determine whether to fulfill a client request that is received from the client via the network, the first server being further configured to select another server, when the client request cannot be fulfilled by the first server; and

a second server configured to perform a handshake with the first server and transparently fulfill the client request with a response packet transmitted to the client by one-way direct data transmission, when the client request cannot be fulfilled by the first server.

10. The system as claimed in claim 9, wherein the first server is connected to the client and the second server.

11. The system as claimed in claim 9, wherein the first server writes the destination address of the second server in a packet representative of the client request.

12. The system as claimed in claim 11, where the first server forwards the packet to the second server.

13. The system as claimed in claim 9, wherein the first server sends an acknowledgment to the client.

14. The system as claimed in claim 9, wherein the first server forwards client data to the second server.

15. The system as claimed in claim 9, wherein the first server writes the source address of the first server in the response packet.

16. A program storage device storing instructions that when executed by a computer perform the method comprising:

performing a handshake between a client and a server;

determining whether to fulfill a client request by the server,

selecting another server, when the client request cannot be fulfilled by the server;

performing a handshake between the server and the other server;

forwarding the client request to the other server for execution, the forwarding being transparent to the client; and

responding by the other server with a one-way direct data transmission to the client.

17. A system for managing a client request in a client-server network having a client, a first server, and a second server, the system comprising:

means for performing a handshake between a client and the first server;

means for determining whether to fulfill a client request by the first server;

means for selecting the second server, when the client request cannot be fulfilled by the first server;

means for performing a handshake between the first server and the second server;

means for transparently forwarding the client request to the second server for execution; and

means for responding to the client by one-way direct data transmission from the second server to the client.

18. A system for managing a client request in a client-server network, the system comprising:

a first server configured to receive a client request from a client via the network and determine whether to fulfill the request using a resource of the first server, wherein the first server hands off the client request to another client in the event that the resource is unavailable; and

a second server configured to establish a link with and receive the client request from the first server via the network, when the first server hands off the client request, and wherein the second server is configured to transparently respond to the client by a one-way direct data transmission from the second server to the client.