Communications on a network

• US 6,718,399 B1
• Filed: 06/10/1996
• Issued: 04/06/2004
• Est. Priority Date: 05/21/1993
• Status: Expired due to Fees

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Candle Distributed Solutions, Inc.
• Inventors: Chernick, Aubrey, Greenblatt, Sam
• Primary Examiner(s): LAO, SUE X
• Application Number:
  US08/660,730
• Time in Patent Office: 2,857 Days
• Field of Search: 395/682, 395/684, 395/683, 395/672, 709/304, 709/302, 709/303, 709/102, 709/330, 709/328, 709/315, 709/310
• US Class Current: 719/330
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An Object Procedure Messaging, or OPM, facility in the form of an internal and external Remote Procedure Call, or RPC, facility uses client and server stubs to transfer messages on both local and remote platforms to reduce multiple calls when a local server object is not available when first called by a local client object. A local memory queue is used to store the message calls for local objects so that the client and server stubs shield the client and server objects from the details of communications therebetween for both local and remote message calls.

Claims

1. A method of communicating via a remote procedure calling (RPC) facility between client and server entities on computer platforms interconnected by a transport network, comprising:

determining if a server is located on the same local platform as a client wishing to communicate a message using an RPC call to the server;

transferring the message to the server via the RPC call on the transport network when the client and server are not located on the same local platform;

storing the message with an object identifier in a local memory queue on the local platform when the client and server are located on the local platform and the server is unavailable to respond to the RPC call, so that the RPC call does not have to be re-tried by the client;

causing the server to interrogate the local memory queue when the server is available to respond to the RPC call, wherein the remote procedure calling facility asynchronously accesses the messages in the local memory queue; and

transferring the message to the server from the local memory queue.

2. The invention of claim 1, wherein the step of determining if a server is located on the same local platform as a client, further comprises:

searching directory services for the location of a server in response to a request from a client to send a message via a RPC call to the server.

3. The invention of claim 2, wherein the step of searching directory services for the location of a server further comprises:

registering the server with directory services.

4. The invention of claim 1 wherein the step of storing the message in a local memory queue further comprises:

using the remote procedure calling facility to access the local memory queue directly.

5. The invention of claim 1 wherein the step of storing the message in a local memory queue further comprises:

forming a local memory queue on the local platform.

7. The invention of claim 1, further comprising:

developing a client stub for communicating with the client and for accomplishing tasks for the client in response to the communications; and

developing a server stub for communicating with the server and for accomplishing tasks for the server in response to the communications,

wherein the client and server are shielded from communications delays resulting from waiting for a response to a communication.

8. The invention of claim 7, wherein the client stub performs the steps of determining if a server is located on the same local platform, transferring the message to the server via the transport network, and storing the message in a local memory queue.

12. The invention of claim 4, wherein the step of using the remote procedure calling facility to access the local memory queue directly, further comprises:

using an RPC call to access the local memory queue directly.

13. The invention of claim 1 wherein the step of using the remote procedure calling facility to asynchronously access the local memory queue further comprises:

using an RPC call to asynchronously access the local memory queue.

6. The invention of claim 6 wherein the step of storing the message in a local memory queue further comprises:

storing a handle associated with the server in the local memory queue.

9. A method of operating a computer network including a plurality of computer platforms interconnected by a network transport system using a remote procedure calling (RPC) facility for communications between objects, comprising:

causing a service requester on a first computer platform to request service from a service provider;

using the RPC facility to obtain the requested service from a selected service provider by issuing an RPC call, further comprising;

determining a location of an eligible service provider for responding to the RPC call;

submitting the RPC call to a network transport system interconnecting the first computer platform to a plurality of additional computer platforms when the location of the eligible service provider is determined not to be on the first platform, operating the network transport system to submit the RPC call to the eligible service provider, operating the eligible service provider to produce a response to the RPC call, submitting the response to the RPC call to the network transport system, and operating the network transport system to return the response to the RPC call to the service requester; and

submitting a message associated with the RPC call to a local memory queue on the first computer platform when the location of the eligible service provider is determined to be on the first platform and the eligible service provider is unavailable to respond to the RPC call, so that the RPC call does not have to be re-tried by the service requester, the eligible service provider asynchronously accessing the message stored in the local memory queue to respond to the RPC call when it is available to respond to the RPC call, and the eligible service provider responding to the service requester identified by the accessed message.

10. The invention of claim 9, wherein the step of determining the location of an eligible service provider, further comprises:

searching a directory services facility on the first platform for the location of an eligible service provider.

11. The invention of claim 9, wherein the step of submitting a message further comprises:

storing a handle associated with the RPC call in the message.