/p5-Event-RPC, Event based transparent Client/Server RPC framework
1.08nb1, Package name:
p5-Event-RPC-1.08nb1, Maintainer: pkgsrc-users
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 and Glib are implemented.
Required to run:
Master sites: SHA1:
Version history: (Expand)
- (2016-06-09) Updated to version: p5-Event-RPC-1.08nb1
- (2016-04-10) Updated to version: p5-Event-RPC-1.08
- (2015-06-12) Updated to version: p5-Event-RPC-1.05nb1
- (2015-01-29) Updated to version: p5-Event-RPC-1.05
- (2014-05-30) Updated to version: p5-Event-RPC-1.04nb1
- (2014-05-14) Updated to version: p5-Event-RPC-1.04
CVS history: (Expand)
| 2016-06-08 21:25:20 by Thomas Klausner | Files touched by this commit (2236) | |
Bump PKGREVISION for perl-5.24.
| 2016-04-10 05:16:37 by Makoto Fujiwara | Files touched by this commit (2) | |
Update to devel/p5-Event-RPC
1.08 Sun Sep 26, 2015, joern
- Just a stable release without changes. I thought
CPAN testers would pick up developer releases
too, but was wrong ;)
1.08_01 Sat Sep 26, 2015, joern
- Support for multiple serialisers: Sereal, CBOR::XS,
JSON::XS and Storable. That's because Storable is
known to be insecure, so this module should not
rely on it.
Great care has been taken to make these changes
up- and downwards compatible, so old clients still
can connect to new servers and vice versa.
Check documentation chapters MESSAGE FORMAT OPTIONS
in Event::RPC, Event::RPC::Server and Event::RPC::Client
manpages for details.
Thanks to mala <mala AT ma.la> for his hint about the
security issues of Storable. You find more details in
http://www.masteringperl.org/2012/12/th … y-problem/
- Proper handling of exceptions which occur at the
server before a remote method is really executed,
e.g. when lookup of the class failed due to
incorrect @INC path.
- Fixed encoding of source files and corrected
the year of all Copyright notices.
| 2015-11-03 04:29:40 by Alistair G. Crooks | Files touched by this commit (1995) |
Add SHA512 digests for distfiles for devel category
Issues found with existing distfiles:
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
| 2015-06-12 12:52:19 by Thomas Klausner | Files touched by this commit (3152) |
Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
| 2015-01-29 09:56:15 by Makoto Fujiwara | Files touched by this commit (2) |
| 2014-05-30 01:38:20 by Thomas Klausner | Files touched by this commit (3049) |
Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
| 2014-05-14 09:19:59 by Hiramatsu Yoshifumi | Files touched by this commit (2) | |
Update devel/p5-Event-RPC to 1.04.
Changes from previous:
1.04 Fri Feb 24, 2014, joern
- Under certain infrequently conditions it could
happen that the server process blocked when
sending a response packet to a client.
- Event::RPC::Client failed loading when no
IO::Socket::SSL is installed.
1.03 Sat Feb 2, 2013, joern
- Added options 'ssl_ca_file and 'ssl_ca_path' options
to Event::RPC::Client, which enable SSL peer verifcation
on the client. Thanks for the report about a security
warning of IO::Socket::SSL to Moritz Bunkus.
1.02 Tue Mar 8, 2011, joern
- Added AnyEvent mainloop implementation.
| 2013-05-31 14:42:58 by Thomas Klausner | Files touched by this commit (2880) |
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.