[pkgsrc/trunk]: pkgsrc/www/p5-HTTP-Async import p5-HTTP-Async-0.09

[abs <abs%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/cf08a572fde4
branches:  trunk
changeset: 543814:cf08a572fde4
user:      abs <abs%pkgsrc.org@localhost>
date:      Mon Jun 23 03:35:35 2008 +0000

description:
import p5-HTTP-Async-0.09

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.

diffstat:

 www/p5-HTTP-Async/DESCR    |  16 ++++++++++++++++
 www/p5-HTTP-Async/Makefile |  18 ++++++++++++++++++
 www/p5-HTTP-Async/distinfo |   5 +++++
 3 files changed, 39 insertions(+), 0 deletions(-)

diffs (51 lines):

diff -r d7469caef76a -r cf08a572fde4 www/p5-HTTP-Async/DESCR
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/www/p5-HTTP-Async/DESCR   Mon Jun 23 03:35:35 2008 +0000
@@ -0,0 +1,16 @@
+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.
diff -r d7469caef76a -r cf08a572fde4 www/p5-HTTP-Async/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/www/p5-HTTP-Async/Makefile        Mon Jun 23 03:35:35 2008 +0000
@@ -0,0 +1,18 @@
+# $NetBSD: Makefile,v 1.1.1.1 2008/06/23 03:35:35 abs Exp $
+
+DISTNAME=      HTTP-Async-0.09
+PKGNAME=       p5-${DISTNAME}
+CATEGORIES=    www perl5
+MASTER_SITES=  ${MASTER_SITE_PERL_CPAN:=HTTP/}
+
+MAINTAINER=    pkgsrc-users%NetBSD.org@localhost
+HOMEPAGE=      http://search.cpan.org/dist/HTTP-Async/
+COMMENT=       Lightweight HTTP client implementation
+
+USE_LANGUAGES= # empty
+PERL5_PACKLIST=        auto/HTTP/Async/.packlist
+
+PKG_DESTDIR_SUPPORT=    user-destdir
+
+.include "../../lang/perl5/module.mk"
+.include "../../mk/bsd.pkg.mk"
diff -r d7469caef76a -r cf08a572fde4 www/p5-HTTP-Async/distinfo
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/www/p5-HTTP-Async/distinfo        Mon Jun 23 03:35:35 2008 +0000
@@ -0,0 +1,5 @@
+$NetBSD: distinfo,v 1.1.1.1 2008/06/23 03:35:35 abs Exp $
+
+SHA1 (HTTP-Async-0.09.tar.gz) = 4bdf206c1685f0ce372e0d50ae3241e09871ef0a
+RMD160 (HTTP-Async-0.09.tar.gz) = e810baa9ce209bceac856e8edb42f3fe930f38cd
+Size (HTTP-Async-0.09.tar.gz) = 16902 bytes