Transparent local RPC optimization

A method for managing communication between a client process and a server process in a distributed computing environment, the client process residing on a host computer that is connected to a physical network having a transport layer and a network layer, comprising the steps of:

• (a) when a remote procedure call is made by the client process, detecting whether a server process identified by the remote procedure call is located on the host computer;
• (b) if the server process is located on the host computer, returning to the client process a first data structure including a protocol sequence defining a communication path through use of the transport and network layers so that the client process obtains a protocol sequence it expects when making the remote procedure call;
• (c) mapping the first data structure to a second data structure, the second data structure including a protocol sequence defining an interprocess communication path between the client process and the server process;
• and
• (d) executing the remote procedure call over the interprocess communication path defined by the protocol sequence in the second data structure instead of using the protocol sequence in the first data structure.

A method for managing communication between a client process and a server process in a distributed computing environment, the client process residing on a host computer that is connected to a physical network having a transport layer and a network layer, comprising the steps of:

• (a) when a remote procedure call is made by the client process, detecting whether a server process identified by the remote procedure call is located on the host computer;
• (b) if the server process is located on the host computer, returning to the client process a first data structure including a connection-oriented protocol sequence defining a communication path through use of the transport and network layers;
• (c) mapping the first data structure to a second data structure, the second data structure including a protocol sequence defining an interprocess communication path between the client process and the server process;
• and
• (d) executing the remote procedure call over the interprocess communication path defined by the protocol sequence in the second data structure;
• wherein the protocol sequence of the second data structure includes a full pathname to a socket file.

A method for managing communication between a client process and a server process in a distributed computing environment when the client process makes a remote procedure call, the client process residing on a host computer that is connected to a physical network having a transport layer and a network layer, the host computer supporting a UNIX-based operating system, comprising the steps of:

• (a) if the server process is located on the host computer, returning to the client process a binding handle having a protocol sequence normally associated with the remote procedure call;
• (b) mapping the protocol sequence normally associated with the remote procedure call into an alternate protocol sequence that establishes an interprocess communication path between the client process and the server process;
• and
• (c) executing the remote procedure call over the interprocess communication path using a send and receive messaging facility of the UNIX-based operating system;
• wherein the protocol sequence associated with the remote procedure call is a connection-oriented protocol "ncacn.sub.-- ip.sub.-- tcp" and the alternate protocol sequence is "ncacn.sub.-- unix.sub.-- stream," where "ncacn" is a connection-oriented RPC protocol, "unix" identifies a UNIX Network Address Family (AF.sub.-- UNIX) communication domain and "stream" identifies a UNIX domain socket.

A method for managing communication between a client process and a server process in a distributed computing environment when the client process makes a remote procedure call, the client process residing on a host computer that is connected to a physical network having a transport layer and a network layer, the host computer supporting a UNIX-based operating system comprising the steps of:

• (a) if the server process is located on the host computer, returning to the client process a binding handle having a protocol sequence normally associated with the remote procedure call;
• (b) mapping the protocol sequence normally associated with the remote procedure call into an alternate protocol sequence that establishes an interprocess communication path between the client process and the server process;
• and
• (c) executing the remote procedure call over the interprocess communication path using a send and receive messaging facility of the UNIX-based operating system;
• wherein the protocol sequence associated with the remote procedure call is a connection-less protocol "ncacn.sub.-- ip.sub.-- udp" and the alternate protocol sequence is "ncadg.sub.-- unix.sub.-- dgram," where "ncadg" is a connection-less RPC protocol, "unix" identifies a UNIX Network Address Family (AF.sub.-- UNIX) communication domain and "dgram" identifies a UNIX domain socket.

A program storage device readable by a host processor and tangibly embodying a program of instructions executable by the host processor to perform a method for managing communications from a client process running on the host processor, the host processor connected to a local area network having a transport layer and a network layer, the method comprising the steps of:

• (a) when a remote procedure call is made by the client process, detecting whether a server process identified by the remote procedure call is located on the host computer;
• (b) if the server process is located on the host computer, returning to the client process a first data structure including a protocol sequence defining a communication path through use of the transport and network layers so that the client process obtains a protocol sequence it expects when making the remote procedure call;
• (c) mapping the first data structure to a second data structure, the second data structure including a protocol sequence defining an interprocess communication path between the client process and the server process;
• and
• (d) executing the remote procedure call over the interprocess communication path defined by the protocol sequence in the second data structure instead of using the protocol sequence in the first data structure.