Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: perl-POE-Component-Client-Ping | Distribution: Mageia |
Version: 1.175.0 | Vendor: Mageia.Org |
Release: 3.mga8 | Build date: Wed Feb 12 14:31:29 2020 |
Group: Development/Perl | Build host: localhost |
Size: 42287 | Source RPM: perl-POE-Component-Client-Ping-1.175.0-3.mga8.src.rpm |
Packager: umeabot <umeabot> | |
Url: http://search.cpan.org/dist/POE-Component-Client-Ping | |
Summary: Concurrent ICMP ping without fork or threads |
POE::Component::Client::Ping is non-blocking ICMP ping client. It lets several other sessions ping through it in parallel, and it lets them continue doing other things while they wait for responses. Ping client components are not proper objects. Instead of being created, as most objects are, they are "spawned" as separate sessions. To avoid confusion (and hopefully not cause other confusion), they must be spawned with a 'spawn' method, not created anew with a 'new' one. PoCo::Client::Ping's 'spawn' method takes a few named parameters:
GPL+ or Artistic
* Wed Feb 12 2020 umeabot <umeabot> 1.175.0-3.mga8 + Revision: 1505788 - Mageia 8 Mass Rebuild + wally <wally> - replace deprecated %makeinstall_std * Thu Sep 20 2018 umeabot <umeabot> 1.175.0-2.mga7 + Revision: 1285463 - Mageia 7 Mass Rebuild
/usr/share/doc/perl-POE-Component-Client-Ping /usr/share/doc/perl-POE-Component-Client-Ping/CHANGES /usr/share/doc/perl-POE-Component-Client-Ping/META.json /usr/share/doc/perl-POE-Component-Client-Ping/META.yml /usr/share/doc/perl-POE-Component-Client-Ping/MYMETA.yml /usr/share/doc/perl-POE-Component-Client-Ping/README /usr/share/man/man3/POE::Component::Client::Ping.3pm.xz /usr/share/perl5/vendor_perl/POE /usr/share/perl5/vendor_perl/POE/Component /usr/share/perl5/vendor_perl/POE/Component/Client /usr/share/perl5/vendor_perl/POE/Component/Client/Ping.pm
Generated by rpm2html 1.8.1
Fabrice Bellet, Sun Oct 13 10:18:22 2024