POE::Component::Client::Twitter is a POE component for Twitter API.
When building network applications, it is often helpful to have
a network accessible control and diagnostic interface. This module
provides such an interface for POE applications. By default, it
provides a fairly limited set of commands but is easily extended
to provide whatever command set you require.
POE::Component::Generic is a POE component that provides a
non-blocking wrapper around any object. It works by forking
a child process with POE::Wheel::Run and creating the object
in the child process. Method calls are then serialised and
sent via STDIN to the child to be handled. Return values are
posted back to your session via STDOUT. This means that all
method arguments and return values must survive serialisation.
If you need to pass coderefs, use "callbacks", "postbacks" or
"factories".
Method calls are wrapped in eval in the child process so that
errors may be propagated back to your session. See "OUTPUT".
Output to STDERR in the child, that is from your object, is
shown only if debug or verbose is set.
STDOUT in the child, that is from your object, is redirected
to STDERR and will be shown in the same circomstances.
POE::Component::Jabber is a module that simplies for the POE
developer, access to the Jabber protocol through the use of one of
the four Client classes. With built in events for common Jabber
packets, all a POE developer need do is provide an event and arguments
for most events so the responses to the requests can be properly
handled by the coder.
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.
A generic publish/subscribe POE::Component that enables POE::Sessions to
publish events to which other POE::Sessions may subscribe.
POEx::Role::TCPServer bundles up the lower level
SocketFactory/ReadWrite combination of wheels into a simple
Moose::Role. It builds upon other POEx modules such as
POEx::Role::SessionInstantiation and POEx::Types.
The events for SocketFactory for and for each ReadWrite instantiated
are methods that can be advised in any way deemed fit. Advising these
methods is actually encouraged and can simplify code for the consumer.
The only method that must be provided by the consuming class is
handle_inbound_data.
This module enables to connect the other process with the S-expression
protocol, like the Swank protocol of the SLIME.
The primary objective is for users to make some Emacs extensions with
the Perl and CPAN.
This class is used by the ResourcePool internally to create
Net::LDAP connections. Its called by the corresponding
ResourcePool::Factory::Net::LDAP object which passes the
parameters needed to establish the Net::LDAP connection.
An object-oriented interface to handle your Amazon S3 storage.