POE::Loop 0.3502 review

POE::Loop is a documentation for POE's event loop bridge interface. SYNOPSIS $kernel->loop_initialize(); $kernel->loop_fin

License: Perl Artistic License File size: 0K Developer: Rocco Caputo

0

POE::Loop is a documentation for POE's event loop bridge interface.

SYNOPSIS

$kernel->loop_initialize();
$kernel->loop_finalize();
$kernel->loop_do_timeslice();
$kernel->loop_run();
$kernel->loop_halt();

$kernel->loop_watch_signal($signal_name);
$kernel->loop_ignore_signal($signal_name);
$kernel->loop_attach_uidestroy($gui_window);

$kernel->loop_resume_time_watcher($next_time);
$kernel->loop_reset_time_watcher($next_time);
$kernel->loop_pause_time_watcher();

$kernel->loop_watch_filehandle($handle, $mode);
$kernel->loop_ignore_filehandle($handle, $mode);
$kernel->loop_pause_filehandle($handle, $mode);
$kernel->loop_resume_filehandle($handle, $mode);

POE's runtime kernel abstraction uses the "bridge" pattern to encapsulate services provided by different event loops. This abstraction allows POE to cooperate with several event loops and support new ones with a minimum amount of work.
POE relies on a relatively small number of event loop services: signal callbacks, time or alarm callbacks, and filehandle activity callbacks.

The rest of the bridge interface is administrative trivia such as initializing, executing, and finalizing event loop.

POE::Kernel uses POE::Loop classes internally as a result of detecting which event loop is loaded before POE is. You should almost never need to use a POE::Loop class directly, although there is some early support for doing so in cases where it's absolutely necessary.

See "Using POE with Other Event Loops" in POE::Kernel for details about actually using POE with other event loops.

Requirements:
Perl