| 1 |
Source: libhttp-async-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: Ernesto Hernández-Novich (USB) <[email protected]>, |
| 4 |
Florian Schlichting <[email protected]> |
| 5 |
Section: perl |
| 6 |
Testsuite: autopkgtest-pkg-perl |
| 7 |
Priority: optional |
| 8 |
Build-Depends: debhelper-compat (= 13) |
| 9 |
Build-Depends-Indep: libnet-https-nb-perl, |
| 10 |
libtest-fatal-perl, |
| 11 |
libtest-http-server-simple-perl, |
| 12 |
libtest-pod-perl, |
| 13 |
libtest-pod-coverage-perl, |
| 14 |
libtest-tcp-perl, |
| 15 |
liburi-perl, |
| 16 |
libwww-perl, |
| 17 |
perl |
| 18 |
Standards-Version: 3.9.8 |
| 19 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libhttp-async-perl |
| 20 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libhttp-async-perl.git |
| 21 |
Homepage: https://metacpan.org/release/HTTP-Async |
| 22 |
|
| 23 |
Package: libhttp-async-perl |
| 24 |
Architecture: all |
| 25 |
Depends: ${misc:Depends}, |
| 26 |
${perl:Depends}, |
| 27 |
liburi-perl, |
| 28 |
libwww-perl |
| 29 |
Suggests: libnet-https-nb-perl |
| 30 |
Multi-Arch: foreign |
| 31 |
Description: module for parallel non-blocking processing of multiple HTTP requests |
| 32 |
Although using the conventional LWP::UserAgent is fast and easy it does have |
| 33 |
some drawbacks - the code execution blocks until the request has been |
| 34 |
completed and it is only possible to process one request at a time. |
| 35 |
HTTP::Async attempts to address these limitations. |
| 36 |
. |
| 37 |
It gives you a 'Async' object that you can add requests to, and then get the |
| 38 |
requests off as they finish. The actual sending and receiving of the requests |
| 39 |
is abstracted. As soon as you add a request it is transmitted, if there are |
| 40 |
too many requests in progress at the moment they are queued. There is no |
| 41 |
concept of starting or stopping - it runs continuously. |
| 42 |
. |
| 43 |
Whilst it is waiting to receive data it returns control to the code that |
| 44 |
called it meaning that you can carry out processing whilst fetching data from |
| 45 |
the network. All without forking or threading - it is actually done using |
| 46 |
select lists. |