AnyEvent-Net-Curl-Queued

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

 - benchmark update (Stanislaw Pusep)
 - Const POD (Stanislaw Pusep)
 - Net::Curl::* constants accessor/cache (Stanislaw Pusep)
 - benchmark fix (Stanislaw Pusep)
 - ++curl benchmark (Stanislaw Pusep)
 - Changes (Stanislaw Pusep)

0.006 2011-10-20T14:02:20
 - added nice comparison chart (Stanislaw Pusep)
 - callback tests (Stanislaw Pusep)
 - Easy: constants cache; on_init/on_finish callbacks (Stanislaw Pusep)
 - Stats: precompute constants (Stanislaw Pusep)
 - benchmark example (Stanislaw Pusep)

0.005 2011-10-19T19:49:29
 - new release (Stanislaw Pusep)
 - recursively update queue test (Stanislaw Pusep)
 - single request in queue test (Stanislaw Pusep)
 - fixed HTTP::Response encapsulation warning when response is empty
   (Stanislaw Pusep)
 - Changes (Stanislaw Pusep)

README  view on Meta::CPAN

    So, this is what CPAN offers to fulfill my needs:

      * Net::Curl: Perl interface to the all-mighty libcurl
      <http://curl.haxx.se/libcurl/>, is well-documented (opposite to
      WWW::Curl);

      * AnyEvent: the DBI of event loops. Net::Curl also provides a nice
      and well-documented example of AnyEvent usage (03-multi-event.pl).

    AnyEvent::Net::Curl::Queued is a glue module to wrap it all together.
    It offers no callbacks and (almost) no default handlers. It's up to you
    to extend the base class AnyEvent::Net::Curl::Queued::Easy so it will
    actually download something and store it somewhere.

 ALTERNATIVES

    As there's more than one way to do it, I'll list the alternatives which
    can be used to implement batch downloads:

      * WWW::Mechanize: no (builtin) parallelism, no (builtin) queueing.
      Slow, but very powerful for site traversal;

lib/AnyEvent/Net/Curl/Queued.pm  view on Meta::CPAN


L<Net::Curl>: Perl interface to the all-mighty L<libcurl|http://curl.haxx.se/libcurl/>, is well-documented (opposite to L<WWW::Curl>);

=item *

L<AnyEvent>: the L<DBI> of event loops. L<Net::Curl> also provides a nice and well-documented example of L<AnyEvent> usage (L<03-multi-event.pl|Net::Curl::examples/Multi::Event>).

=back

L<AnyEvent::Net::Curl::Queued> is a glue module to wrap it all together.
It offers no callbacks and (almost) no default handlers.
It's up to you to extend the base class L<AnyEvent::Net::Curl::Queued::Easy> so it will actually download something and store it somewhere.

=head2 ALTERNATIVES

As there's more than one way to do it, I'll list the alternatives which can be used to implement batch downloads:

=over 4

=item *



( run in 0.381 second using v1.01-cache-2.11-cpan-9b1e4054eb1 )