| 1 |
Source: libmessage-passing-zeromq-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: |
| 4 |
Jonas Smedegaard <[email protected]>, |
| 5 |
Section: perl |
| 6 |
Testsuite: autopkgtest-pkg-perl |
| 7 |
Priority: optional |
| 8 |
Build-Depends: |
| 9 |
debhelper-compat (= 13), |
| 10 |
Build-Depends-Indep: |
| 11 |
libanyevent-perl <!nocheck>, |
| 12 |
libfile-pushd-perl <!nocheck>, |
| 13 |
libjson-perl <!nocheck>, |
| 14 |
libmessage-passing-perl <!nocheck>, |
| 15 |
libmodule-install-perl, |
| 16 |
libmoo-perl <!nocheck>, |
| 17 |
libmoox-types-mooselike-perl <!nocheck>, |
| 18 |
libnamespace-clean-perl <!nocheck>, |
| 19 |
libposix-atfork-perl <!nocheck>, |
| 20 |
libsub-name-perl <!nocheck>, |
| 21 |
libtask-weaken-perl <!nocheck>, |
| 22 |
libtest-simple-perl <!nocheck>, |
| 23 |
libtry-tiny-perl <!nocheck>, |
| 24 |
libzmq-ffi-perl <!nocheck>, |
| 25 |
perl, |
| 26 |
Standards-Version: 4.7.2 |
| 27 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libmessage-passing-zeromq-perl |
| 28 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libmessage-passing-zeromq-perl.git |
| 29 |
Homepage: https://metacpan.org/release/Message-Passing-ZeroMQ |
| 30 |
|
| 31 |
Package: libmessage-passing-zeromq-perl |
| 32 |
Architecture: all |
| 33 |
Depends: |
| 34 |
${misc:Depends}, |
| 35 |
${perl:Depends}, |
| 36 |
libanyevent-perl, |
| 37 |
libfile-pushd-perl, |
| 38 |
libmessage-passing-perl, |
| 39 |
libmoo-perl, |
| 40 |
libmoox-types-mooselike-perl, |
| 41 |
libnamespace-clean-perl, |
| 42 |
libposix-atfork-perl, |
| 43 |
libsub-name-perl, |
| 44 |
libtask-weaken-perl, |
| 45 |
libtry-tiny-perl, |
| 46 |
libzmq-ffi-perl, |
| 47 |
Description: input and output messages to ZeroMQ |
| 48 |
Message::Passing::ZeroMQ is a ZeroMQ transport for Message::Passing. |
| 49 |
. |
| 50 |
Designed for use as a log transport and aggregation mechanism for perl |
| 51 |
applications, allowing you to aggregate structured and non-structured |
| 52 |
log messages across the network in a non-blocking manner. |
| 53 |
. |
| 54 |
Clients (i.e. users of the Message::Passing::Output::ZeroMQ class) |
| 55 |
connect to a server (i.e. a user of the Message::Passing::Input::ZeroMQ |
| 56 |
class) via ZeroMQ's pub/sub sockets. These are setup to be lossy and |
| 57 |
non-blocking, meaning that if the log-receiver process is down or slow, |
| 58 |
then the application will queue a small (and configurable) amount of |
| 59 |
logs on its side, and after that log messages will be dropped. |
| 60 |
. |
| 61 |
Whilst throwing away log messages isn't a good thing to do, or |
| 62 |
something that you want to happen regularly, in many (especially web |
| 63 |
application) contexts, network logging being a single point of failure |
| 64 |
is not acceptable from a reliability and graceful degradation |
| 65 |
standpoint. |
| 66 |
. |
| 67 |
The application grinding to a halt as a non-essential centralised |
| 68 |
resource is unavailable (e.g. the log aggregation server) is |
| 69 |
significantly less acceptable than the loss of non-essential logging |
| 70 |
data. |