Perl Object Environment: Difference between revisions

Revision as of 22:46, 19 July 2013

Revision as of 09:02, 1 September 2013

Line 12:

The informal architecture consists of a set of layers with a [[Kernel (computer science)|kernel]] on the bottom. This tiny kernel represents the events layer which operates as the main loop of each running POE instance. The first call is to the "event dispatcher" - '''POE::Kernel'''.

The POE::Kernel namespace contains a suite of functions which are plugged-in to the kernel itself. These loop abstractions are designed after POE's standardized event loop bridge interface - '''POE::Loop'''. These can be mixed and matched as needed to provide runtime services and a lean facility for [[interprocess communication]]. The basic functions are '''POE::Loop::Event''', '''POE::Loop::Poll''' and '''POE::Loop::Select'''. Also available are '''POE::Loop::Tk''' and '''POE::Loop::Gtk''' thatwhich offer hooks into other loop bridges in the external environment. If that isn't enough, the POE::Loop kernel abstraction provides reusable signal callbacks, time or alarm callbacks, and filehandle activity callbacks as well as administrative functions such as initializing, executing, and finalizing event loops.

There is also a higher level packaging framework - POE::Macro and a debugging utility for testing them called POE::Preprocessor. This framework has yielded '''POE::Macro::UseBytes'''.