13 lines
1.0 KiB
Markdown
13 lines
1.0 KiB
Markdown
# perl-Event-RPC
|
|
|
|
Event::RPC consists of a server and a client library. The server exports a list of classes and methods, which are allowed to be called over the network. More specific it acts as a proxy for objects created on the server side (on demand of the connected clients) which handles client side methods calls with transport of method arguments and return values.
|
|
|
|
The object proxy handles refcounting and destruction of objects created by clients properly. Objects as method parameters and return values are handled as well (although with some limitations, see below).
|
|
|
|
For the client the whole thing is totally transparent - once connected to the server it doesn't know whether it calls methods on local or remote objects.
|
|
|
|
Also the methods on the server newer know whether they are called locally or from a connected client. Your application logic is not affected by Event::RPC at all, at least if it has a rudimentary clean OO design.
|
|
|
|
For details on implementing servers and clients please refer to the man pages of Event::RPC::Server and Event::RPC::Client.
|
|
|