POE::Sugar::Args - Get "pretty", OO representation of args. River stage one • 4 direct dependents • 4 total dependents

Exports sweet_args This function will get @_ from the calling state by doing deep, dark voodoo. It will construct the "POE::Sugar::Args" object for you. Very handy. Methods new Constructs an object. Expects all of @_ that's passed to an event state. ...

CWEST/POE-Sugar-Args-1.3 - 30 Sep 2003 22:04:01 GMT

POE::Component - event driven objects or subsystems River stage three • 410 direct dependents • 570 total dependents

POE "components" are event-driven modules that generally encapsulate mid- to high-level program features. For example, POE::Component::Client::DNS performs message-based asynchronous resolver lookups. POE::Component::Server::TCP is a basic asynchrono...

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

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 GMT

MooseX::POE::SweetArgs - sugar around MooseX::POE event arguments River stage two • 27 direct dependents • 48 total dependents

Normally, when using MooseX::POE, subs declared as events need to use POE macros for unpacking @_, e.g.: my ($self, $foo, $bar) = @_[OBJECT, ARG0..$#_]; Using MooseX::POE::SweetArgs as a metaclass lets you avoid this, and just use @_ as normal: my ($...

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

POE::Session::Multiplex - POE session with object multiplexing River stage one • 2 direct dependents • 3 total dependents

POE::Session::Multiplex allows you to have multiple objects handling events from a single POE::Session. A standard POE design is to have one POE::Session per object and to address each object using session IDs or aliases. POE::Session::Multiplex take...

GWYN/POE-Session-Multiplex-0.0600 - 18 May 2011 17:39:12 GMT

MooX::Role::POE::Emitter - Pluggable POE event emitter role for cows River stage one • 3 direct dependents • 5 total dependents

Consuming this Moo::Role gives your class a POE::Session capable of processing events via loaded plugins and/or emitting them to registered "listener" sessions. It is derived from POE::Component::Syndicator by BINGOS, HINRIK, APOCAL et al, but with m...

AVENJ/MooX-Role-POE-Emitter-1.001002 - 06 Mar 2015 00:33:24 GMT

POE::Session::PlainCall - POE sessions with plain perl calls River stage one • 3 direct dependents • 4 total dependents

POE::Session::PlainCall provides standard perl object-oriented call signature to your POE event handlers. This allows for your methods and functions to be called either via POE events or as normal methods and functions. It also requires less typing t...

GWYN/POE-Session-PlainCall-0.0301 - 03 Sep 2013 18:20:52 GMT

7 results (0.035 seconds)