POE::Session and its subclasses translate events from POE::Kernel's generic dispatcher into the particular calling conventions suitable for application code. In design pattern parlance, POE::Session classes are adapters between POE::Kernel and applic...

POE::Session::YieldCC extends POE::Session to allow "continuations". A new method on the session object, "yieldCC" is introduced. "yieldCC" takes as arguments a state name (in the current session) and a list of arguments. Control is yield to that sta...

This POE::Session subclass helps you integrate POE and Irssi scripting. It connects the signals and commands handlers you define as POE events with the Irssi machinery. It also tries to clean up as much as possible when the script gets unloaded, by r...

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

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

This module provides an object based POE session. This object will perform the necessary actions for the lifetime of the session. This includes signal handling. Due to the nature of POE events, they can not be inherited from, but the event handlers c...

A simple helper module that lets you connect callback names from your .glade file with methods of an object. These methods are called as POE callback or postback methods. POE::Session::GladeXML automatically determines whether gtk expects the signal ...

This module's purpose is to save you some boilerplate code around POE::Session->create() method. Just inherit your class from POE::Session::Attribute and define some states using attributes. Method "spawn()" in your package will be provided by POE::S...

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

POE::Session::MessageBased exists mainly to replace @_[KERNEL, etc.] with message objects that encapsulate various aspects of each event. It also exists as an example of a subclassed POE::Session, in case someone wants to create new callback or Sessi...

POE::Session::MultiDispatch is a drop in replacement for POE::Session that adds callback dispatch functionality to POE sessions. Each event may have multiple handlers associated with it. Fine control over the order of execution is available using hel...

POE::XUL::Session provides half of the margic for POE::XUL::Application. It implements perl-like event invocation. It makes sure the change manager and other bits of global data are always available to event handlers. It deals with most of the house ...

Provides an attribute handler that does some bookkeeping for state handlers. There have been a few of these classes for POE. This is probably the most minimal. It supports only the inline attribute syntax. but that seems sufficient for cranking up a ...

This supervision handle will watch POE::Sessions...

This is a factory object that creates POE::Component::Supervisor::Handle::Session objects....

The wrapper is very thin, so most of the useful documentation can be found in the Net::OSCAR module. Create a new connection with $oscar = POE::Component::OSCAR->new(); Though it has an object interface to make coding simpler, this actually spawns a ...