#Corba idl code#

#Corba idl code#

The real function then does what it needs to and returns to the server stub which can package up the return information (both return code and any or variables) and pass it back to the client stub. The server's stub receives the information, unpacks it and passes it to the real function. In the server, there's a 'listener' process that will receive that information and pass it to the server. This can be the same machine or a different machine, it doesn't really matter - one of the advantages of RPC is to be able to move servers around at will. In this example, instead of calling function in the same program, main calls a client stub function (with the same prototype as function) which is responsible for packaging up the information and getting it across the wire to another process, via the comms channel. It's very similar to a function prototype in C but the end result is slightly different, such as in the following graphic: +-+ RPC needs to create stub functions for the client and a server, using the IDL information. There have been many variations of this such as Sun RPC, ONC RPC, DCE RPC and so on.Д«asically, you use an IDL to specify the interface between client and server so that the RPC mechanism can create the code stubs required to call functions across the network. An interface definition language (IDL) is used to set up communications between clients and servers in remote procedure calls (RPC).