POE::Declare - A POE abstraction layer for conciseness and simplicity River stage one • 6 direct dependents • 6 total dependents

POE is a very powerful and flexible system for doing asynchronous programming. But it has the reputation of being difficult to learn, with a somewhat confusing set of abstractions. In particular, it can be tricky to resolve POE's way of programming w...

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

POE::Request - a common message class for POE::Stage River stage one • 1 direct dependent • 1 total dependent

POE::Request objects encapsulate messages passed between POE::Stage objects. Each request includes a destination (the stage and method to call), optional data to be sent to the destination method (args), and optional hints where to send responses (on...

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

POE::Callback - object wrapper for callbacks with lexical closures River stage one • 1 direct dependent • 1 total dependent

POE::Callback wraps coderefs in magic that makes certain lexical variables persistent between calls. It's used internally by the classes that comprise POE::Stage....

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

POE::Resource - internal resource managers for POE::Kernel River stage three • 328 direct dependents • 417 total dependents

POE manages several types of information internally. Its Resource classes are mix-ins designed to manage those types of information behind tidy, mostly private interfaces. This was done to facilitate testing and a conversion to C without the need to ...

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

POE::Loop::Tk - a bridge that allows POE to be driven by Tk River stage one • 5 direct dependents • 8 total dependents

POE::Loop::Tk replaces POE's internal event loop with the Tk module. This allows programs to use both POE and Tk at the same time. POE::Loop::Tk implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please se...

RCAPUTO/POE-Loop-Tk-1.305 - 22 Aug 2013 01:40:09 GMT

POE::Component - event driven objects or subsystems River stage three • 328 direct dependents • 417 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

POE::Resources - loader of POE resources River stage three • 328 direct dependents • 417 total dependents

POE::Kernel is internally split into different resources that are separately managed by individual mix-in classes. POE::Resources is designed as a high-level macro manager for POE::Resource classes. Currently it implements a single method, load(), wh...

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

POE::Loop::Gtk - a bridge that allows POE to be driven by Gtk 1.x River stage one • 1 direct dependent • 1 total dependent

POE::Loop::Gtk replaces POE's internal event loop with the Gtk module. This allows programs to use both POE and Gtk 1.x at the same time. Please see POE::Loop::Glib for more modern Gtk2 and Gtk3 support. POE::Loop::Gtk implements the interface docume...

RCAPUTO/POE-Loop-Gtk-1.306 - 21 Aug 2013 23:29:36 GMT

POE::Declarative - write POE applications without the mess River stage one • 2 direct dependents • 2 total dependents

Taking the lessons learned from writing dispatchers and templates in Jifty and Template::Declare, I've applied the same declarative language to POE. The goal is to make writing a POE application less painful so that I can concentrate on the more impo...

HANENKAMP/POE-Declarative-0.09 - 11 Sep 2010 16:41:28 GMT

POE::Loop::Event - a bridge that allows POE to be driven by Event.pm River stage one • 1 direct dependent • 1 total dependent

POE::Loop::Event implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details....

RCAPUTO/POE-Loop-Event-1.305 - 21 Aug 2013 23:03:51 GMT

POE::Loop::Prima - bridge between Prima and POE River stage one • 2 direct dependents • 2 total dependents

This class is an implementation of the abstract POE::Loop interface. It follows POE::Loop's public interface exactly. Therefore, please see POE::Loop for its documentation....

KARASIK/POE-Loop-Prima-1.03 - 08 Jun 2015 10:26:41 GMT

POE::Loop::Select - a bridge that allows POE to be driven by select(2) River stage three • 328 direct dependents • 417 total dependents

POE::Loop::Select implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details....

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

POE::Loop::Kqueue - a bridge that supports kqueue(2) from POE River stage one • 1 direct dependent • 1 total dependent

This class is an implementation of the abstract POE::Loop interface. It follows POE::Loop's public interface exactly. Therefore, please see POE::Loop for its documentation. kqueue(2) currently supported in FreeBSD 4.1+, NetBSD 2.0, OpenBSD 2.9+, MacO...

GDSL/POE-Loop-Kqueue-0.02 - 14 Mar 2005 14:38:05 GMT

POE::Loop::IO_Poll - a bridge that allows POE to be driven by IO::Poll River stage three • 328 direct dependents • 417 total dependents

POE::Loop::IO_Poll implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details....

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

POE::Resource::SIDs - internal session ID manager for POE::Kernel River stage three • 328 direct dependents • 417 total dependents

POE::Resource::SIDs is a mix-in class for POE::Kernel. It provides the features necessary to manage session IDs. It is used internally by POE::Kernel, so it has no public interface....

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

POE::Loop::TkCommon - common code between the POE/Tk event loop bridges River stage one • 5 direct dependents • 8 total dependents

POE::Loop::TkCommon is a mix-in class that supports common features between POE::Loop::Tk and POE::Loop::TkActiveState. All Tk bridges implement the interface documented in POE::Loop. Therefore, please see POE::Loop for more details....

RCAPUTO/POE-Loop-Tk-1.305 - 22 Aug 2013 01:40:09 GMT

POE::XUL::RDF - RDF builder class River stage one • 1 direct dependent • 1 total dependent

Primitive RDF generation for XUL trees....

GWYN/POE-XUL-0.0601 - 06 Sep 2016 15:39:14 GMT

POE::Loop::Wx - a bridge that supports wxPerl's event loop from POE River stage one • 1 direct dependent • 1 total dependent

This class is an implementation of the abstract POE::Loop interface. It follows POE::Loop's public interface exactly. Therefore, please see POE::Loop for its documentation....

MIKE/POE-Loop-Wx-0.04 - 29 Nov 2007 17:16:36 GMT

POE::Loop::EV - a bridge that supports EV from POE River stage one • 1 direct dependent • 1 total dependent

This class is an implementation of the abstract POE::Loop interface. It follows POE::Loop's public interface exactly. Therefore, please see POE::Loop for its documentation....

DBOOK/POE-Loop-EV-0.14 - 12 Feb 2017 01:09:56 GMT

POE::Resource::Events - internal event manager for POE::Kernel River stage three • 328 direct dependents • 417 total dependents

POE::Resource::Events is a mix-in class for POE::Kernel. It hides the complexity of managing POE's events from even POE itself. It is used internally by POE::Kernel, so it has no public interface....

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

909 results (0.033 seconds)