Home > Repositories > base > perl-Event-RPC > perl-Event-RPC (i586)
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.
Required by
Provided files
perl-Event-RPC: Event::RPC - Event based transparent Client/Server RPC framework
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.
| Name: | perl-Event-RPC |
| Release: | 1.11-1mamba |
| Architecture: | noarch |
| Group: | System/Libraries/Perl |
| Size: | 81.57 kB |
| Upstream URL: | https://www.cpan.org/ |
| Source RPM: | perl-Event-RPC |
| Brothers | Provides | Obsoletes | Requires | Recommends |
|---|---|---|---|---|
| perl(Event::RPC) = 0:1.11 perl(Event::RPC::AuthPasswdHash) perl(Event::RPC::Client) perl(Event::RPC::Connection) perl(Event::RPC::LogConnection) perl(Event::RPC::Logger) perl(Event::RPC::Loop) perl(Event::RPC::Loop::AnyEvent) perl(Event::RPC::Loop::Event) perl(Event::RPC::Loop::Glib) perl(Event::RPC::Message) perl(Event::RPC::Message::CBOR) perl(Event::RPC::Message::JSON) perl(Event::RPC::Message::Negotiate) perl(Event::RPC::Message::Sereal) perl(Event::RPC::Message::SerialiserBase) perl(Event::RPC::Message::Storable) perl(Event::RPC::Server) perl-Event-RPC = 0:1.11-1mamba | perl >= 0:5.36.0 [1] perl(AnyEvent) [1] perl(CBOR::XS) [1] perl(Carp) [1] perl(Event) [1] perl(Event::RPC) [1] perl(FileHandle) [1] perl(Glib) [1] perl(IO::Socket) [1] perl(JSON::XS) >= 0:3.0 [1] perl(Sereal) [1] perl(Socket) [1] perl(Storable) [1] perl(Sys::Hostname) [1] perl(base) [1] perl(strict) [1] perl(utf8) [1] |
