Manual Reference Pages - POE::LOOP::ANYEVENT (3)
POE::Loop::AnyEvent - AnyEvent event loop support for POE
use POE qw( Loop::AnyEvent );
# The rest of your program goes here.
# There should be little or no changes necessary.
# All POE APIs and most modules should work with no changes.
POE::Loop::AnyEvent replaces POEs default select() event loop with
AnyEvent. This allows POE programs to transparently use most of the
event loops AnyEvent can provide.
POE::Loop::AnyEvent changes POEs internal implementation without
altering its APIs. By design, nearly all software that are already
uses POE should continue to work normally without any changes.
It may seem obvious, but AnyEvent::Impl::POE and POE::Loop::AnyEvent
are mutually exclusive of one another. Using both would result in a
deadlock as each event system called upon the other in infinite
This deadlock also affects AnyEvents support of Wx and Prima.
AnyEvent doesnt natively support these event loops. Instead it takes
advantage of POEs more flexible, comprehensive, and open event loop
POE::Sessions callback() and postback() methods simplify callbacks
from plain-coderef systems like Tk and AnyEvent to POEs named event
handlers. Please see POE::Session for more details.
POE::Loop::AnyEvent implements the private POE::Loop API. Please see
POE::Loop for an explanation of that API, especially if youd like
to publish support for a new event loop. POE is structured so that
new event loops can be supported without core distribution changes.
Also see POE::Test::Loops for over 35 test files and more than 490
tests you can use for free when writing new POE::Loop modules.
Chris Williams <email@example.com>
COPYRIGHT AND LICENSE
This software is copyright (c) 2013 by Chris Williams.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
|perl v5.20.3 ||POE::LOOP::ANYEVENT (3) ||2013-06-05 |
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.