Search results for "dist:RMI transparent"
RMI - Remote Method Invocation with transparent proxies
RMI stands for Remote Method Invocation. The RMI modules allow one process to have virtual object "stubs" which are proxies for real objects in another process. When methods are invoked on the proxy, the method actually runs in the other process. Whe...
SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 UTC
RMI::Node - base class for RMI::Client and RMI::Server
This is the base class for RMI::Client and RMI::Server. RMI::Client and RMI::Server both implement a wrapper around the RMI::Node interface, with convenience methods around initiating the sending or receiving of messages. An RMI::Node object embeds t...
SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 UTC
RMI::Client - connection to an RMI::Server
This is the base class for a standard RMI connection to an RMI::Server. In most cases, you will create a client of some subclass, typically RMI::Client::Tcp for a network socket, or RMI::Client::ForkedPipes for a private out-of-process object server....
SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 UTC
RMI::ProxyObject - used internally by RMI for "stub" objects
This class is the real class of all transparent proxy objects, though objects of this class will attempt to hide that fact. This is an internal class used by RMI::Client and RMI::Server nodes. Objects of this class are never constructed explicitly by...
SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 UTC