RMI - Remote Method Invocation with transparent proxies River stage zero No dependents

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 GMT

RMI::Server - service RMI::Client requests from another process River stage zero No dependents

This is the base class for RMI::Servers, which accept requests via an IO handle of some sort, execute code on behalf of the request, and send the return value back to the client. When the RMI::Server responds to a request which returns objects or ref...

SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 GMT

RMI::Node - base class for RMI::Client and RMI::Server River stage zero No dependents

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 GMT

RMI::Client - connection to an RMI::Server River stage zero No dependents

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 GMT

RMI::ProxyObject - used internally by RMI for "stub" objects River stage zero No dependents

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 GMT

RMI::ProxyReference - used internally by RMI to tie references River stage zero No dependents

When an refrerence is detected in the params or return value for an RMI call, the sending RMI::Node (client sending params or server sending results) captures a reference to the item internally, generates an "id" for that object, and sends the "id" a...

SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 GMT

RMI::Server::ForkedPipes - service RMI::Client::ForkedPipes requests River stage zero No dependents

This subclass of RMI::Server is used by RMI::Client::ForkedPipes when it forks a private server for itself....

SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 GMT

RMI::Client::ForkedPipes - an RMI::Client implementation with a private out-of-process server River stage zero No dependents

This subclass of RMI::Client forks a child process, and starts an RMI::Server::ForkedPipes in that process. It is useful for testing more complex RMI, and also to do things like use two versions of a module at once in the same program....

SAKOHT/RMI-0.10 - 19 Oct 2010 05:49:23 GMT

8 results (0.046 seconds)