Ubuntu
libhttp-async-perl package

libhttp-async-perl 0.16-1 source package in Ubuntu

Changelog

libhttp-async-perl (0.16-1) unstable; urgency=low


  [ Salvatore Bonaccorso ]
  * Change Vcs-Git to canonical URI (git://anonscm.debian.org).
  * Change search.cpan.org based URIs to metacpan.org based URIs.

  [ Florian Schlichting ]
  * Imported Upstream version 0.11, 0.16.
  * Bumped Standards-Version to 3.9.4 (no change).
  * Bumped copyright years.
  * Email change: Florian Schlichting -> <email address hidden>.

 -- Florian Schlichting <email address hidden>  Sat, 25 May 2013 19:30:20 +0200

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Saucy: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
libhttp-async-perl_0.16-1.dsc 2.2 KiB f29831208a7e888c66ea1f993986b54be0c8dee4f92a99d8a2bde23d6d018049
libhttp-async-perl_0.16.orig.tar.gz 18.2 KiB b9561934b38ab233f327c36a809a7f61451e27a9b7ce316cef1f834363239a55
libhttp-async-perl_0.16-1.debian.tar.gz 2.5 KiB 7a9879fbb78ca644fcba5ec564b44f9d93013c1bd275cb3eda5c25de114777e3

Available diffs

No changes file available.

Binary packages built by this source

libhttp-async-perl: module for parallel non-blocking processing of multiple HTTP requests

 Although using the conventional LWP::UserAgent is fast and easy it does have
 some drawbacks - the code execution blocks until the request has been
 completed and it is only possible to process one request at a time.
 HTTP::Async attempts to address these limitations.
 .
 It gives you a 'Async' object that you can add requests to, and then get the
 requests off as they finish. The actual sending and receiving of the requests
 is abstracted. As soon as you add a request it is transmitted, if there are
 too many requests in progress at the moment they are queued. There is no
 concept of starting or stopping - it runs continuously.
 .
 Whilst it is waiting to receive data it returns control to the code that
 called it meaning that you can carry out processing whilst fetching data from
 the network. All without forking or threading - it is actually done using
 select lists.