POE::Framework::MIDI - A simplified front end to the POE::Framework::MIDI environment River stage one • 1 direct dependent • 1 total dependent

This module allows you to specify the data required by the POE::Framework::MIDI environment without having to dive into the guts of the framework....

SMCNABB/POE-Framework-MIDI-0.09 - 19 Mar 2006 17:15:55 GMT

Reflex::POE::Session - Watch events from a POE::Session object. River stage one • 6 direct dependents • 6 total dependents

Reflex::POE::Session allows a Reflex::Base object to receive events from a specific POE::Session instance, identified by the session's ID. Authors are encouraged to encapsulate POE sessions within Reflex objects. Most users should not need use Reflex...

RCAPUTO/Reflex-0.100 - 02 Apr 2017 21:56:28 GMT

POE::Filter::Hessian - Translate datastructures to and from Hessian for transmission via a POE ReadWrite wheel. River stage one • 1 direct dependent • 1 total dependent

The goal of POE::Filter::Hessian is to combine the versatility of POE with the Hessian serialization protocol. As POE::Filter::Hessian is based on Hessian::Client which is still in a fairly experimental state, it can also be considered to be highly e...

HEYTRAV/POE-Filter-Hessian-1.00 - 02 Mar 2010 18:50:45 GMT

POE::Component::MXML - Perl extension for parsing Minimal XML specs River stage one • 1 direct dependent • 1 total dependent

MXML is a Minimalist XML, without frills such as CDATA, attributes or entities. Refer to http://www.docuverse.com/smldev/minxmlspec.html for a spec....

JGOFF/POE-Component-MXML-0.03 - 27 Sep 2003 23:00:03 GMT

POE::Stage::Resolver - a simple non-blocking DNS resolver River stage one • 1 direct dependent • 1 total dependent

POE::Stage::Resolver is a simple non-blocking DNS resolver. For now it uses Net::DNS::Resolver for the bulk of its work. It returns Net::DNS::Packet objects in its "success" responses. Please see the documentation for Net::DNS....

RCAPUTO/POE-Stage-0.060 - 28 Jul 2009 18:15:54 GMT

POE::Filter::XML::NS - Provides constants that return appropriate namespace strings River stage one • 3 direct dependents • 4 total dependents

POE::Filter::XML::NS provides namespace constants for use within POE::Filter::XML::Nodes (or any other representation) that requires namespace matching. The following export tags are explained below: :JABBER ":JABBER" tag will import various useful c...

NPEREZ/POE-Filter-XML-1.140700 - 11 Mar 2014 22:00:01 GMT

POE::Component::Cron - Schedule POE Events using a cron spec River stage one • 2 direct dependents • 2 total dependents

This component extends POE::Component::Schedule by adding an easy way t specify event schedules using a simple cron spec....

CFEDDE/POE-Component-Cron-0.021 - 27 Jun 2009 23:13:06 GMT

POE::Filter::ThruPut - a POE filter that passes data through unchanged whilst counting bytes sent and received No river data available

POE::Filter::ThruPut passes data through without changing it, but counts the bytes sent and received. It follows POE::Filter's API and can be used with POE::Filter::Stackable....

BINGOS/POE-Filter-ThruPut-1.00 - 20 Jul 2018 10:27:05 GMT

IO::Async::Loop::POE - use IO::Async with POE River stage zero No dependents

This subclass of IO::Async::Loop uses POE to perform its work. The entire "IO::Async" system is represented by a single long-lived session within the "POE" core. It fully supports sharing the process space with "POE"; such resources as signals are pr...

PEVANS/IO-Async-Loop-POE-0.05 - 02 Mar 2013 17:47:56 GMT

POE::Component::ICal - Schedule POE events using rfc2445 recurrences River stage one • 1 direct dependent • 1 total dependent

This component extends POE::Component::Schedule by adding an easy way to specify event schedules using rfc2445 recurrence. See DateTime::Event::ICal for the syntax, the list of the authorized parameters and their use....

LOSYME/POE-Component-ICal-0.130020 - 02 Jan 2013 21:07:10 GMT

POE::Declare::Object - Base class for all POE::Declare classes River stage one • 6 direct dependents • 6 total dependents

POE::Declare::Object provides the base package that delivers core functionality for all instantiated POE::Declare objects. Functionality and methods defined here are available in all POE::Declare classes....

ADAMK/POE-Declare-0.59 - 03 Feb 2012 11:30:05 GMT

POE::Component::Pcap - POE Interface to Net::Pcap River stage one • 1 direct dependent • 1 total dependent

POE::Component::Pcap provides a wrapper for using the Net::Pcap module from POE programs. The component creates a separate session which posts events to a specified session and state when packets are available. ARGUMENTS Alias The alias for the Pcap ...

FLETCH/POE-Component-Pcap-0.04 - 08 Jul 2003 15:26:09 GMT

POE::Devel::Profiler - profiles POE programs River stage one • 1 direct dependent • 1 total dependent

This module profiles POE programs, in the same way the Devel::DProf family of modules do. Currently, POE::Devel::Profiler will profile the following: Program start/end Session create/destruction alarm_set delay_set signal alias_set yield/post/call fr...

APOCAL/POE-Devel-Profiler-0.02 - 18 Oct 2004 20:40:57 GMT

POE::Component::Fuse - Using FUSE in POE asynchronously River stage one • 2 direct dependents • 2 total dependents

This module allows you to use FUSE filesystems in POE. Basically, it is a wrapper around Fuse and exposes it's API via events. Furthermore, you can use Filesys::Virtual to handle the filesystem. The standard way to use this module is to do this: use ...

APOCAL/POE-Component-Fuse-0.05 - 02 Feb 2009 05:24:00 GMT

POE::Filter::FastCGI - Parse and create FastCGI requests River stage one • 1 direct dependent • 1 total dependent

Parses the FastCGI binary protocol into a perl array with the CGI environment and any POST or other data that is sent. Accepts either POE::Component::FastCGI::Response objects or a simple hash reference via "put" and converts into the FastCGI binary ...

GETTY/POE-Component-FastCGI-0.19 - 09 Oct 2011 22:24:34 GMT

POE::Component::TSTP - A POE Component to handle Ctrl-Z River stage one • 1 direct dependent • 1 total dependent

By default, POE applications do not respond to Ctrl-Z due to slightly strange signal handling semantics. This module fixes that. You can pass in two options to the "create()" routine: * Alias An *Alias* for the component. By default it is called "tst...

MSERGEANT/POE-Component-TSTP-0.02 - 17 Dec 2002 18:07:13 GMT

MooseX::POE::Aliased - A sane alias attribute for your MooseX::POE objects. River stage two • 24 direct dependents • 38 total dependents

This role provides an "alias" attribute for your MooseX::POE objects. The attribute can be set, causing the current alias to be cleared and the new value to be set....

GETTY/MooseX-POE-0.215 - 25 Apr 2012 16:10:05 GMT

POE::Request::Recall - encapsulates responses to POE::Request::Emit River stage one • 1 direct dependent • 1 total dependent

POE::Request::Recall objects encapsulate responses to POE::Request::Emit objects. They are created internally by POE::Request::Emit's recall() method. They are quite like POE::Request objects, except that they are not created with a "stage" parameter...

RCAPUTO/POE-Stage-0.060 - 28 Jul 2009 18:15:54 GMT

POE::Request::Upward - internal base class for POE::Stage response messages River stage one • 1 direct dependent • 1 total dependent

POE::Stage messages are generally asynchronous, which means that multiple "calls" can be in play at once. To track them, POE::Stage uses a call tree rather than a call stack. POE::Request::Upward is a base class for POE::Request messages that flow up...

RCAPUTO/POE-Stage-0.060 - 28 Jul 2009 18:15:54 GMT

POE::Resource::Clock - internal clock used for ordering the queue River stage three • 328 direct dependents • 417 total dependents

POE::Resource::Clock is a helper module for POE::Kernel. It provides the features to keep an internal monotonic clock and a wall clock. It also converts between this monotonic clock and the wall clock. The monotonic clock is used to keep an ordered q...

RCAPUTO/POE-1.367 - 03 Jun 2015 14:20:42 GMT

910 results (0.024 seconds)