System and method for performing remote requests with an on-line service network

• US 5,956,509 A
• Filed: 08/18/1995
• Issued: 09/21/1999
• Est. Priority Date: 08/18/1995
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kevner, Gene D.
• Primary Examiner(s): Maung, Zami
• Application Number:
  US08/516,184
• Time in Patent Office: 1,495 Days
• Field of Search: 395/684, 395/200.33, 395/200.47, 395/200.53, 395/200.48, 395/200.49, 395/685, 395/683
• US Class Current: 719/330
• CPC Class Codes: G06F 13/14 Handling requests for interconnection or transfer

Abstract

A remote request system and method monitors and controls the execution of remote requests on an on-line services network. When a remotely located client sends a remote request to the on-line service network, the remote request system monitors the remote request while returning operating control back to the client while the remote request remains pending in the on-line service network. The remote request system also provides for the concurrent execution of multiple pending remote requests, provides status information about each remote request, provides for the cancellation of a pending remote request and optimizes the use of memory. In addition, the remote request system dynamically allocates memory when data blocks of unknown size are transmitted over the on-line services network.

Claims

1. A remote request system for creating and monitoring remote requests sent to an interactive, on-line services network, comprising:

at least one client application executing in a end-user computer, said client application containing at least one execution thread, said execution thread capable of generating a plurality of concurrently pending remote requests; and

a client request layer executing in said end-user computer and in communication with said execution thread, said client request layer configured to receive said remote requests and to uniquely label each of said remote requests, said client request layer further configured to monitor said pending remote requests while said execution thread continues execution, wherein said unique label contains a first identifier that identifies a set of remote requests, a second identifier that identifies a remote request function and a third identifier that identifies each instance of said remote request.

2. The remote request system of claim 1 further comprising an object-oriented data structure in communication with said remote request layer, said data structure storing at least one object for each of said pending remote requests.

3. The remote request system of claim 2, wherein said unique label in each of said uniquely labeled remote requests identifies at least one of said objects in said data structure.

4. The remote request system of claim 3 wherein said unique label identifies a remote request interface.

5. The remote request system of claim 4 wherein said second identifier identifies a remote request method.

6. The remote request system of claim 5 wherein said third identifier identifies a remote request instance.

7. The remote request system of claim 1, wherein said remote request system contains a plurality of said end-user computers connected to an on-line network via a wide area network and wherein said remote request layer in each of said end-user computers sends said uniquely labeled remote requests to said on-line network via said wide area network.

8. The remote request system of claim 3 wherein said data structure contains a method object for each instance of said remote request.

9. A machine for monitoring the status of remote procedure calls sent to an interactive, on-line services network, comprising:

at least one client application executing in a computer, said client application capable of sending at least one remote procedure call to an on-line network;

a status data structure resident in said computer, said status data structure containing status information about said remote procedure call, wherein said status information allows said client application to obtain the progress of a data upload or a data download operation with the on-line network;

a remote procedure layer in communication with said client application, said status data structure and a wide area network, said remote procedure layer executing in said computer, said remote procedure layer responsive to said remote procedure calls generated by said client application, wherein said remote procedure layer subdivides said remote procedure call into a plurality of remote messages and sends said remote messages to said on-line network via said wide area network; and

a status routine in communication with said status data structure, said remote procedure layer and said client application, said status routine executing in said computer and responsive to each of said remote messages wherein said status routine obtains status information from said remote messages and updates said status data structure with said status information.

10. The machine of claim 9, wherein said status data structure communicates said status information to said client applications.

11. The machine of claim 10, wherein said client application uses said status information to create a fuel gauge that indicates the progress of a remote procedure call.

12. The machine of claim 11, wherein said remote procedure call uploads data to said on-line network.

13. The machine of claim 10, wherein said remote procedure layer receives a plurality of response messages from said on-line network and wherein said status routine obtains status information from said response messages and updates said status data structure with said status information.

14. The machine of claim 13, wherein said remote procedure call downloads data from said on-line network.

15. A remote request system for creating and monitoring the status of remote requests sent to an interactive, on-line services network, comprising:

at least one client application executing in a computer, said client application capable of sending a plurality of concurrently pending remote requests to an on-line network;

a data structure resident in said computer, said data structure containing a plurality of identifiers that uniquely identify said remote requests, said data structure further containing at least one status data structure linked to said identifiers;

a request layer in communication with said client application sand said on-line network, said request layer executing in said computer, said client applications invoking said request layer to generate said remote requests wherein said request layer uses said identifiers to locate and update said status data structure when said remote requests are sent to said on-line network; and

wherein said plurality of identifiers contain a first identifier that uniquely identifies a remote request interface, a second identifier that identifies a remote request method, and a third identifier that identifies a remote request instance.

16. The remote request system of claim 15, wherein said request layer periodically communicates said status information to said client application.

17. The remote request system of claim 15, wherein said remote requests are remote procedure calls.

18. The remote request system of claim 15, wherein said data structure further contains a plurality of identification objects that contain said plurality of identifiers.

19. The remote request system of claim 18, wherein said data structure further contains a plurality of status objects linked to said plurality of identification objects, said status objects containing at least one of said status data structures.

20. A distributed on-line network for processing remote requests comprising:

a plurality of interconnected servers, said interconnected servers containing at least one service application that executes a plurality of remote requests;

an object-oriented service data structure resident in said on-line service, said service data structure containing a plurality of request objects that uniquely identify each of said remote requests, each of said request objects containing a plurality of identifiers that identify a remote request type and the origin of said remote request;

a service request layer in communication with said service data structure and said service application, wherein said service request layer uses said identifiers in each of said request objects to direct said service application to execute said remote request and wherein said service request layer combines said identifiers with the results of said remote request to create at least one response message,

wherein said plurality of identifiers contain a first identifier that uniquely identifies a remote request interface, a second identifier that identifies a remote request method, and a third identifier that identifies a remote request instance.

21. The distributed on-line network in claim 20 wherein said service request layer uses said identifiers in said response messages to identify the destination of said response messages.

22. In a remote request system, a method for creating and monitoring remote requests sent to an on-line network, comprising:

creating multiple pending remote requests with an end-user computer;

creating a plurality of identifiers that uniquely identify each of said remote requests, said plurality of identifiers containing a first identifier that uniquely identifies a set of remote requests, a second identifier that uniquely identifies a remote request function and a third identifier that uniquely identifies each instance of said remote request;

storing said plurality of identifiers in a data structure;

combining said first, second and third identifiers to create at least one remote message; and

sending said remote message via said wide area network to an on-line network.

23. The method of claim 22 wherein said step of creating a plurality of identifiers further creates a plurality of objects that store said plurality of identifiers.

24. The method as defined in claim 22 further comprising the step of creating a status data structure for each of said plurality of remote requests.

25. The method as defined in claim 24 further comprising the step of updating said status data structure when said remote messages are sent to said on-line network.

26. The method as defined in claim 24 further comprising the step of updating said status data structure when said remote messages are sent to said on-line network.

27. The method as defined in claim 24 further comprising the step of accessing said status data structure to obtain status information about said remote requests.

28. The method as defined in claim 22 further comprising the steps of:

creating a cancel request that cancels at least one of said remote requests, said cancel request containing a cancel command and said identifiers that uniquely identify at least one remote request; and

sending said cancel request to said on-line network.

29. The method as defined in claim 22 further comprising the step of creating a dynamic object in response to a remote request for a data block of unknown size.

30. The method as defined in claim 29 further comprising the step of expanding said dynamic data structure to hold said data block of unknown size in continuous sections of memory when said end-user computer receives said block of unknown size from said on-line service.

31. The method as defined in claim 30 wherein said step of expanding said dynamic data structure comprises subdividing said dynamic data structure into a plurality of data buffers.

32. The method as defined in claim 31 further comprising the step of accessing said data buffers before all of said data block of unknown size is received from said on-line network.

33. The method as defined in claim 32 further comprising the step of deleting at least one of said plurality of data buffers before receiving all of said data block of unknown size from said on-line network.

34. In a computer, a method for monitoring the status of remote procedure calls sent to an interactive, on-line services network, comprising:

creating at least one remote procedure call that is sent to an on-line network;

creating a status data structure for said remote procedure call wherein said status data structure contains status information about said remote procedure call, wherein said status information allows said client application to obtain the progress of a data upload or a data download operation with the on-line network;

subdividing said remote procedure call into a plurality of remote messages;

sending each of said remote messages to said on-line network via a wide area network;

obtaining status information from said remote messages; and

updating said status data structure with said status information.

35. The method of claim 34, wherein said status information comprises the amount of data each of said remote messages sends to said on-line network.

36. The method of claim 35, further comprising the step of accessing said status data structure to obtain the progress of a data upload to said on-line network.

37. The method of claim 36 further comprising the steps of:

receiving a plurality of response messages from said on-line network;

obtaining status information from said response messages; and

updating said status data structure with said status information.

38. The method of claim 37, further comprising the step of accessing said status data structure to obtain the progress of a data download from said on-line network.

39. The method of claim 34, wherein said step of creating a status data structure further comprises the creation of a plurality of identifiers that uniquely identify said remote request and the linking of said status data structure to said plurality of identifiers.

40. The method of claim 39, wherein said step of updating said status data structure comprises the use of said plurality of identifiers contained within said request messages to locate said status data structure.

41. A data stream for sending a plurality of remote messages to an on-line network, said data stream comprising:

a plurality of remote procedure messages, each of said remote procedure messages corresponding to a pending remote request, said remote procedure messages further comprising;

a header, said header containing an interface identifier, a method identifier, and a instance identifier that identifies the instance of said remote request, wherein said interface identifier, said method identifier and said instance identifier uniquely identify one of said pending remote requests; and

a plurality of data packets.

42. The data stream of claim 41 wherein said interface identifier is a one-byte value.

43. The data stream of claim 42 wherein said method identifier is a one-byte value.

44. The data stream of claim 43 wherein said instance identifier is at least a one-byte value.

45. The data stream of claim 41 wherein each of said plurality of data packets includes a type field, a length field and a data field.

46. The data stream of claim 41 wherein said plurality of remote messages for one of said remote requests is interleaved with a plurality of remote messages for another of said remote requests.

47. A remote request system for creating and monitoring remote requests sent to an interactive, on-line services network, comprising:

at least one client application executing in a end-user computer, said client application containing at least one execution thread, said execution thread capable of generating a plurality of concurrently pending remote requests;

a client request layer executing in said end-user computer and in communication with said execution thread, said client request layer configured to receive said remote requests and to uniquely label each of said remote requests, said client request layer further configured to monitor said pending remote requests while said execution thread continues execution; and

an object-oriented data structure in communication with said remote request layer, said data structure storing at least one object for each of said pending remote requests;

wherein said unique label in each of said uniquely labeled remote requests identifies at least one of said objects in said data structure, and said unique label identifies a remote request interface.

48. The remote request system of claim 47, wherein said unique label contains a first identifier that identifies a set of remote requests, a second identifier that identifies a remote request function and a third identifier that identifies each instance of said remote request.

49. The remote request system of claim 47, wherein said second identifier identifies a remote request method.

50. The remote request system of claim 49, wherein said third identifier identifies a remote request instance.

51. The remote request system of claim 47, wherein said data structure contains a method object for each instance of said remote request.

52. The remote request system of claim 47, wherein said remote request system contains a plurality of said end-user computers connected to an on-line network via a wide area network and wherein said remote request layer in each of said end-user computers sends said uniquely labeled remote requests to said on-line network via said wide area network.

53. A remote request system for creating and monitoring remote requests sent to an interactive, on-line services network, comprising:

at least one client application executing in a end-user computer, said client application containing at least one execution thread, said execution thread capable of generating a plurality of concurrently pending remote requests; and

a client request layer executing in said end-user computer and in communication with said execution thread, said client request layer configured to receive said remote requests and to uniquely label each of said remote requests, said client request layer further configured to monitor said pending remote requests while said execution thread continues execution;

an object-oriented data structure in communication with said remote request layer, said data structure storing at least one object for each of said pending remote requests;

wherein said unique label in each of said uniquely labeled remote requests identifies at least one of said objects in said data structure; and

wherein said data structure contains a method object for each instance of said remote request.

54. The remote request system of claim 53, wherein said unique label contains a first identifier that identifies a set of remote requests, a second identifier that identifies a remote request function and a third identifier that identifies each instance of said remote request.

55. The remote request system of claim 53, wherein said unique label identifies a remote request interface.

56. The remote request system of claim 55, wherein said second identifier identifies a remote request method.

57. The remote request system of claim 56, wherein said third identifier identifies a remote request instance.

58. The remote request system of claim 53, wherein said remote request system contains a plurality of said end-user computers connected to an on-line network via a wide area network and wherein said remote request layer in each of said end-user computers sends said uniquely labeled remote requests to said on-line network via said wide area network.