Stateless distributed computer architecture with server-oriented state-caching objects maintained on network or client

• US 7,127,514 B2
• Filed: 12/28/2000
• Issued: 10/24/2006
• Est. Priority Date: 12/28/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hunt, Galen C.
• Primary Examiner(s): Caldwell, Andrew
• Assistant Examiner(s): WILLETT, STEPHAN F
• Application Number:
  US09/752,114
• Publication Number:
  US 20020087657A1
• Time in Patent Office: 2,126 Days
• Field of Search: 709/227, 709/228, 709/237, 709/246, 709/248, 709/249, 707/201
• US Class Current: 709/227
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A stateless distributed computer architecture allows state-caching objects, which hold server state information, to be maintained on a client or network rather than on a server. In one implementation, the computer architecture implements object-oriented program modules according to a distributed component object model (DCOM). Using an object-oriented network protocol (e.g., remote procedure call), a client-side application calls through an application program interface (API) to a program object residing at a server computer. The program object, responsive to the call, creates a state caching object that contains state information pertaining to the client connection. The server inserts the state-caching object into a local thread context and processes the request to generate a reply. The server subsequently attaches the state-caching object to the reply and returns them both to the client. The client stores the state-caching object for later communication with the server. When the client subsequently calls the program object at the server, the client submits the state-caching object along with the request packet. The server uses the state information in the state-caching object to quickly restore state for the client reconnection. In this manner, the server can offload its state information to other computing devices in the distributed architecture, thereby improving scalability. In another implementation, the network itself caches the server-oriented state-caching object.

Claims

1. A stateless distributed computer system, comprising:

a network having one or more network components to route requests from a first endpoint device to a second endpoint device and to route replies from the second endpoint device back to the first endpoint device, wherein at least one reply contains state information pertaining to the second endpoint device; and

the network being configured to maintain the state information and to reassociate the state information with a subsequent request from the first endpoint device to the second endpoint device, and wherein multiple network components continually route the state information amongst themselves to preserve the state information.

2. A stateless distributed computer system as recited in claim 1, wherein state information is embodied as a data object.

3. Computer-readable media in a network system comprising computer-executable instructions that, when executed on one or more processors, direct the system to:

route, via one or more network components, a request from a first endpoint device to a second endpoint device;

route, via the one or more network components, replies from the second endpoint device back to the first endpoint device, wherein at least one reply contains state information pertaining to the second endpoint device;

continually route the state information among multiple network components to preserve the state information; and

reassociate the state information with a subsequent request being routed from the first endpoint device to the second endpoint device.

4. A system, comprising:

network means for routing requests from a client to a server and for routing a reply from the server back to the client, wherein the reply contains state a information pertaining to the server; and

the network means comprising means for maintaining the state information within the network means and for reassociating the state information with a subsequent request from the client to the server, and means for continually routing the state information among network components to preserve the state infonnation.

5. A system as recited in claim 4, wherein state information is embodied as a data object.

6. A method comprising:

routing, via a network, a request from a first endpoint device to a second endpoint device;

routing, via the network, a reply from the second endpoint device back to the first endpoint device, wherein the reply contains state information pertaining to the second endpoint device;

maintaining the state information at the network by continually routing the state information along network components of the network to preserve the state information; and

reassociating the state information with a subsequent request being routed from the first endpoint device to the second endpoint device.

7. A method as recited in claim 6, wherein the state information is embodied as a data object.

8. A method comprising:

routing a request from a client to a server over a network;

routing a reply from the server back to the client over the network, wherein the reply contains state information pertaining to the server; and

maintaining the state information on the network while awaiting a subsequent request from the client to the server by continually routing the state information among network components of the network to preserve the state information.

9. A method as recited in claim 8, wherein the state information is embodied as a data object.

10. A method as recited in claim 8, further comprising reassociating the state information with a subsequent request being routed from the client to the server.