File: control

package info (click to toggle)
libevent-rpc-perl 1.10-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster
  • size: 456 kB
  • sloc: perl: 2,344; makefile: 2
file content (45 lines) | stat: -rw-r--r-- 1,926 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Source: libevent-rpc-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>,
           Xavier Guimard <x.guimard@free.fr>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper (>= 10)
Build-Depends-Indep: libanyevent-perl,
                     libcbor-xs-perl,
                     libevent-perl,
                     libglib-perl,
                     libio-socket-ssl-perl,
                     libjson-xs-perl,
                     libsereal-perl,
                     netbase,
                     perl
Standards-Version: 4.1.5
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libevent-rpc-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libevent-rpc-perl.git
Homepage: https://metacpan.org/release/Event-RPC

Package: libevent-rpc-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libcbor-xs-perl,
         libevent-perl,
         libglib-perl,
         libio-socket-ssl-perl
Recommends: libanyevent-perl,
            libjson-xs-perl,
            libsereal-perl
Description: Event based transparent Client/Server RPC framework
 Event::RPC supports you in developing Event based networking client/server
 applications with transparent object/method access from the client to the
 server. Network communication is optionally encrypted using IO::Socket::SSL.
 Several event loop managers are supported due to an extensible API. Currently
 Event, Glib and AnyEvent are implemented.
 .
 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.