POE::Component::Client::Ping - a non-blocking ICMP ping client River stage one • 4 direct dependents • 4 total dependents

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. Inst...

RCAPUTO/POE-Component-Client-Ping-1.175 - 19 Jul 2017 02:47:38 UTC

POE::Kernel - an event-based application kernel in Perl River stage three • 414 direct dependents • 574 total dependents

POE::Kernel is the heart of POE. It provides the lowest-level features: non-blocking multiplexed I/O, timers, and signal watchers are the most significant. Everything else is built upon this foundation. POE::Kernel is not an event loop in itself. For...

BINGOS/POE-1.368 - 02 Feb 2020 13:39:17 UTC

Task::POE::All - All of POE on CPAN River stage zero No dependents

This task contains all distributions under the POE namespace....

APOCAL/Task-POE-All-1.102 - 09 Nov 2014 11:07:41 UTC

POE::Component::IRC - A fully event-driven IRC client module River stage three • 56 direct dependents • 129 total dependents

POE::Component::IRC is a POE component (who'd have guessed?) which acts as an easily controllable IRC client for your other POE components and sessions. You create an IRC component and tell it what events your session cares about and where to connect...

BINGOS/POE-Component-IRC-6.90 - 05 Sep 2017 18:19:13 UTC

POE::Component::LaDBI - POE Component that spawns a perl subprocess to handle non-blocking access to the DBI API. River stage one • 1 direct dependent • 1 total dependent

LaDBI Session Events "shutdown" This tells the LaDBI session to shutdown. It takes two optional arguments, $cause and $errstr. Both arguments get posted back to all registered sessions and all outstanding requests. For registered sessions the "Offlin...

SEGAN/POE-Component-LaDBI-1.2.1 - 18 Jul 2004 20:45:49 UTC

POE::Component::Pluggable - A base class for creating plugin-enabled POE Components. River stage two • 8 direct dependents • 14 total dependents

POE::Component::Pluggable is a base class for creating plugin enabled POE Components. It is a generic port of POE::Component::IRC's plugin system. If your component dispatches events to registered POE sessions, then POE::Component::Pluggable may be a...

BINGOS/POE-Component-Pluggable-1.28 - 20 Feb 2017 13:38:36 UTC

POE::Component::Lightspeed - The romping grounds of IKC2 River stage one • 1 direct dependent • 1 total dependent

In the Lightspeed world, you have either a server or a client. Obviously, the clients connect to servers. In order for server kernels to connect to other kernels, you can run a client and a server session in the same process. Please familiarize yours...

APOCAL/POE-Component-Lightspeed-0.05 - 20 May 2005 11:44:21 UTC

POE::Component::IKC::Responder - POE IKC state handler River stage two • 9 direct dependents • 11 total dependents

This module implements POE IKC state handling. The responder handles posting states to foreign kernels and calling states in the local kernel at the request of foreign kernels. There are 2 interfaces to the responder. Either by sending states to the ...

GWYN/POE-Component-IKC-0.2402 - 07 Jul 2014 18:41:38 UTC

POE::Component::Client::Rcon - an implementation of the Rcon remote console protocol. River stage one • 1 direct dependent • 1 total dependent

POE::Component::Client::Rcon is an implementation of the Rcon protocol -- the protocol commonly used to remotely administer Half-Life, Quake, and RTCW (Return to Castle Wolfenstein) servers. It is capable of handling multiple Rcon requests simultaneo...

ACHEN/POE-Component-Client-Rcon-0.23 - 04 Oct 2003 06:33:29 UTC

POE::Component::Client::Halo - an implementation of the Halo query protocol. River stage one • 1 direct dependent • 1 total dependent

POE::Component::Client::Halo is an implementation of the Halo query protocol. It was reverse engineered with a sniffer and two cups of coffee. This is a preliminary release, based version 1.00.01.0580 of the dedicated server (the first public release...

ACHEN/POE-Component-Client-Halo-0.2 - 11 Oct 2003 17:52:05 UTC

POE::Component::IKC::ClientLite - Small client for IKC River stage two • 9 direct dependents • 11 total dependents

ClientLite is a small, pure-Perl IKC client implementation. It is very basic because it is intented to be used in places where POE wouldn't fit, like mod_perl. It handles automatic reconnection. When you post an event, ClientLite will try to send the...

GWYN/POE-Component-IKC-0.2402 - 07 Jul 2014 18:41:38 UTC

POE::Component::DebugShell::Jabber - Component to allow interactive peeking into a running POE application via Jabber River stage one • 1 direct dependent • 1 total dependent

This component allows for interactive peeking into a running POE application. "spawn()" creates a Jabber client shell equipped with various debug commands. After it connects, stdout and stderr is redirected to all users in the user hash, AND anyone w...

XANTUS/POE-Component-DebugShell-Jabber-0.04 - 27 Feb 2006 19:13:09 UTC

POE::Component::Client::Traceroute - A non-blocking traceroute client River stage one • 2 direct dependents • 2 total dependents

POE::Component::Client::Traceroute is a non-blocking Traceroute client. It lets several other sessions traceroute through it in parallel, and it lets them continue doing other things while they wait for responses. Starting Traceroute Client Tracerout...

AHOYING/POE-Component-Client-Traceroute-0.21 - 22 Aug 2006 23:27:19 UTC

POE::Component::AssaultCube::ServerQuery::Server - Holds the server info River stage one • 1 direct dependent • 1 total dependent

This module represents a server for the PoCo to ping. There are a few values to twiddle. Constructor This module uses Moose, so you can pass either a hash or a hashref to the constructor. The attributes are: server The server ip. NOTE: Input in the f...

APOCAL/Games-AssaultCube-0.04 - 10 Dec 2009 08:33:54 UTC

14 results (0.05 seconds)