Method and system for network marshalling of interface pointers for remote procedure calls

• US 5,724,588 A
• Filed: 06/07/1995
• Issued: 03/03/1998
• Est. Priority Date: 11/13/1992
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Jung, Edward K., Hill, Richard Douglas, Chan, Shannon John, Wittenberg, Craig Henry, Mitchell, Alexander Adams, Williams, Antony S., Atkinson, Robert G., Leach, Paul, Corbett, Tom
• Primary Examiner(s): Kriess, Kevin A.
• Application Number:
  US08/485,046
• Time in Patent Office: 1,000 Days
• Field of Search: 395/680, 395/683, 395/684
• US Class Current: 719/328
• CPC Class Codes: G06F 9/4488 Object-oriented
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

A computer method and system for passing a pointer to an interface from a server process to a client process. In a preferred embodiment, the server process instantiates an object that has multiple interfaces. The server process identifies an interface to pass to the client process and creates a stub object for receiving a request to invoke a function member of the interface and for invoking the requested function member upon receiving the request. The server process then sends an identifier of the stub to the client process. When the client process receives the identifier of the stub, it instantiates a proxy object for receiving requests to invoke a function member of the interface and for sending the request to the identified stub. The client process can then invoke the function members of the interface by invoking function members of the proxy object. The proxy object sends a request to the identified stub. The identified stub then invokes the corresponding function member of the interface.

Claims

1. A method in a computer system for providing a client with access to a client implementation of an interface corresponding to a server implementation of the interface provided by a server, comprising:

under control of the server, sending to the client an indication of unmarshalling code and information for use by the unmarshalling code to provide the client implementation of the interface that corresponds to the server implementation of the interface; and

under control of the client,

receiving the indication of the unmarshalling code and the information; and

executing the indicated unmarshalling code to generate a pointer to the client implementation of the interface in accordance with the received information

whereby the client uses the generated pointer to access the client implementation of the interface.

2. The method of claim 1 wherein the interface has a function member and including:

under control of the server,

creating a stub for, in response to receiving a request to invoke the function member of the server implementation of the interface, invoking the function member of the server implementation of the interface, and wherein the information sent to the client includes a reference to the created stub; and

under control of the client,

using the generated pointer to invoke the function member of the client implementation of the function member, wherein the invoked function member sends a request to the stub referenced in the received information to invoke the function member of the server implementation of the interface.

3. The method of claim 1 wherein the interface has a function member that provides a behavior, wherein the server implementation of the interface has associated state information and wherein the sending of information to the client includes the state information, and including

under control of the client,

using the generated pointer to invoke the function member of the client implementation of the interface wherein the invoked function member accesses the received state information to provide the behavior of the function member without requesting that the server invoke the function member of the server implementation of the interface.

4. The method of claim 3 wherein the state information is immutable information.

5. The method of claim 1 wherein the interface has a query interface function member for providing a reference to another interface that is accessible to an implementation of the interface.

6. The method of claim 1 including:

under control of the server,

determining whether the interface has associated custom unmarshalling code; and

when the interface has associated custom unmarshalling code, sending to the client an indication of the custom unmarshalling code.

7. The method of claim 6 including:

when the interface does not have associated custom unmarshalling code, sending to the client an indication of standard marshalling code.

8. The method of claim 6 including:

under control of the server,

invoking a query interface function member of the server implementation of the interface to determine whether the server implementation of the interface has access to a custom marshalling interface; and

when the server implementation of the interface has access, invoking a function member of the custom marshalling interface to provide the indication of the unmarshalling code and the information for use by the unmarshalling code.

9. The method of claim 1 wherein the interface has a function member, wherein the server implementation of the interface has associated state information that is stored in memory shared with the client, and wherein the information sent by the server includes a reference to the state information in the shared memory and including:

under control of the client,

invoking the function member of the client implementation of the interface wherein the invoked function member accesses the state information using the reference to the state information in shared memory.

10. The method of claim 1 wherein the indication of the unmarshalling code identifies a class of a proxy object and before executing the unmarshalling code, instantiating a proxy object of the identified class and invoking a function member of the proxy object to control the execution of the unmarshalling code.

11. A computer system for providing a client with access to a client interface through which the client accesses a server, comprising:

server means for sending to the client an indication of unmarshalling code and information for use by the unmarshalling code to provide the client interface; and

client means for receiving the indication of the unmarshalling code and the information, and executing the indicated unmarshalling code to generate a pointer to the client interface in accordance with the received information whereby the client uses the generated pointer to access the server through the client interface.

12. The system of claim 11 wherein the interface has a function member and,

the server means further includes means for creating a stub, the stub for, in response to receiving a request to invoke the function member of the server implementation of the interface, invoking the function member of the server implementation of the interface, and means for sending to the client a reference to the created stub;

and

the client means further includes means for using the generated pointer to invoke the function member of the client implementation of the function member, wherein the invoked function member sends a request to the stub referenced in the received information to invoke the function member of the server implementation of the interface.

13. The system of claim 11 wherein the interface has a query interface function member for providing a reference to another interface that is accessible to an implementation of the interface.

14. The system of claim 11 wherein the server means further includes means for determining whether the interface has associated custom unmarshalling code, and means for sending to the client an indication of the custom unmarshalling code when the interface has associated custom unmarshalling code.

15. The system of claim 11 wherein the indication of the unmarshalling code identifies a class of a proxy object and before executing the unmarshalling code, the client means instantiates a proxy object of the identified class and invokes a function member of the proxy object to control the execution of the unmarshalling code.

16. A method in a computer system for unmarshalling a pointer to a server interface sent from a server to a client, the server interface for providing a service to the client, comprising:

receiving an indication of unmarshalling code and information describing the server interface of the server;

locating the unmarshalling code indicated by the received indication;

executing the located unmarshalling code to generate a pointer to a client interface; and

using the generated pointer to invoke a function member of the client interface wherein the invoked function member provides the service to the client using the information describing the server interface.

17. The method of claim 16 wherein the invoked function member requests that a function member of the server interface of the server provide the service.

18. The method of claim 16 wherein the indication of the unmarshalling code identifies a class of a proxy object and before executing the unmarshalling code, instantiating a proxy object of the identified class and invoking a function member of the proxy object to control the execution of unmarshalling code.

19. A method in a computer system for custom marshalling of a pointer to an object from a server to a client, the object having data members and function members comprising:

instantiating the object;

determining whether custom marshalling code is provided for the object;

when it is determined that custom marshalling code is provided, executing custom marshalling code to provide an indication of custom unmarshalling code and information describing the object to the custom unmarshalling code; and

when it is determined that custom marshalling code is not provided, executing standard marshalling code to provide an indication of standard unmarshalling code and information describing the object to the standard unmarshalling code; and

sending the provided indication and information to the client so that the client can execute the indicated unmarshalling code to provide a custom or standard proxy object through which to request services of the instantiated object.

20. The method of claim 19 including:

creating a stub for, in response to receiving a request to invoke a function member of the object, invoking the function member of the object; and

sending to the client a reference to the created stub.

21. The method of claim 19 including:

determining whether the object has associated custom unmarshalling code; and

when the object has associated custom unmarshalling code, sending to the client an indication of the custom unmarshalling code.

22. The method of claim 21 including:

when the interface does not have associated custom unmarshalling code, sending to the client an indication of standard marshalling code.

23. A method in a comptuer system for marshalling a pointer to an interface from a first server to a client, the pointer pointing to an interface of the first server that is marshalled from a second server, the interface having a function member providing a behavior, wherein the client, the first server, and the second server each have an implementation of the function member, wherein the implementation of the function member of the first server requests the implementation of the function member of the second server to perform the behavior of the function member, comprising:

under control of the first server, sending to the client an indication of unmarshalling code and information indicating the second server; and

under control of the client,

receiving the indication of the unmarshalling code and the information; and

executing the indicated unmarshalling code to generate a pointer to an interface with a client implementation of the function member that when invoked requests the second server to provide the behavior

whereby when the client implementation of the function member is invoked, then the client requests the second server to perform the behavior without requesting the first server to perform the behavior.

24. A computer-readable medium containing instructions for causing a computer system to provide a client with access to a client implementation of an interface corresponding to a server implementation of the interface provided by a server by:

under control of the server, sending to the client an indication of unmarshalling code and information for use by the unmarshalling code to provide the client implementation of the interface that corresponds to the server implementation of the interface; and

under control of the client,

receiving the indication of the unmarshalling code and the information; and

executing the indicated unmarshalling code to generate a pointer to the client implementation of the interface in accordance with the received information.

25. The computer-readable medium of claim 24 wherein the interface has a function member and including:

under control of the server,

creating a stub for, in response to receiving a request to invoke the function member of the server implementation of the interface, invoking the function member of the server implementation of the interface, and wherein the information sent to the client includes a reference to the created stub; and

under control of the client,

using the generated pointer to invoke the function member of the client implementation of the function member, wherein the invoked function member sends a request to the stub referenced in the received information to invoke the function member of the server implementation of the interface.

26. The computer-readable medium of claim 24 wherein the interface has a function member that provides a behavior, wherein the server implementation of the interface has associated state information and wherein the sending of information to the client includes the state information, and including

under control of the client,

using the generated pointer to invoke the function member of the client implementation of the interface wherein the invoked function member accesses the received state information to provide the behavior of the function member without requesting that the server invoke the function member of the server implementation of the interface.

27. The computer-readable medium of claim 26 wherein the state information is immutable information.

28. The computer-readable medium of claim 24 wherein the interface has a query interface function member for providing a reference to another interface that is accessible to an implementation of the interface.

29. The computer-readable medium of claim 24 including:

under control of the server,

determining whether the interface has associated custom unmarshalling code; and

when the interface has associated custom unmarshalling code, sending to the client an indication of the custom unmarshalling code.

30. The computer-readable medium of claim 29 including:

when the interface does not have associated custom unmarshalling code, sending to the client an indication of standard marshalling code.

31. The computer-readable medium of claim 29 including:

under control of the server,

invoking a query interface function member of the server implementation of the interface to determine whether the server implementation of the interface has access to a custom marshalling interface; and

when the server implementation of the interface has access, invoking a function member of the custom marshalling interface to provide the indication of the unmarshalling code and the information for use by the unmarshalling code.

32. The computer-readable medium of claim 24 wherein the interface has a function member, wherein the server implementation of the interface has associated state information that is stored in memory shared with the client, and wherein the information sent by the server includes a reference to the state information in the shared memory and including:

under control of the client,

invoking the function member of the client implementation of the interface wherein the invoked function member accesses the state information using the reference to the state information in shared memory.

33. The computer-readable medium of claim 24 wherein the indication of the unmarshalling code identifies a class of a proxy object and before executing the unmarshalling code, instantiating a proxy object of the identified class and invoking a function member of the proxy object to control the execution of the unmarshalling code.

34. A computer-readable medium containing instructions for causing a computer system to marshal a pointer to an object from a server to a client, the object having data members and function members by:

instantiating the object;

determining whether the custom marshalling code is provided for the object;

when it is determined that custom marshalling code is provided, executing custom marshalling code to provide an indication of custom unmarshalling code and information describing the object to the custom unmarshalling code; and

when it is determined that custom marshalling code is not provided, executing standard marshalling code to provide an indication of standard unmarshalling code and information describing the object to the standard unmarshalling code; and

sending the provided indication and information to the client so that the client can execute the indicated unmarshalling code to provide a custom or standard proxy object through which to request services of the instantiated object.

35. The computer-readable medium of claim 34 including:

creating a stub for, in response to receiving a request to invoke a function member of the object, invoking the function member of the object; and

sending to the client a reference to the created stub.

36. The computer-readable medium of claim 34 including:

determining whether the object has associated custom unmarshalling code; and

when the object has associated custom unmarshalling code, sending to the client an indication of the custom unmarshalling code.

37. The computer-readable medium of claim 36 including:

when the interface does not have associated custom unmarshalling code, sending to the client an indication of standard marshalling code.