Perl Object Environment - Revision history

NotAG on AWB: replace {{manual}} with {{how-to}} per TfD

2025-01-03T13:02:18Z

replace {{manual}} with {{how-to}} per TfD

← Previous revision		Revision as of 13:02, 3 January 2025
Line 4:		Line 4:
	{{essay-like\|date=October 2018}}		{{essay-like\|date=October 2018}}
	{{overly detailed\|date=October 2018}}		{{overly detailed\|date=October 2018}}
	{{~~manual~~\|article\|date=January 2017}}		{{how-to\|article\|date=January 2017}}
	}}		}}
	The '''Perl Object Environment''' ('''POE''') is a [[library (computing)\|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.		The '''Perl Object Environment''' ('''POE''') is a [[library (computing)\|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.

	From CPAN:		From CPAN:
Line 19:		Line 19:
	The POE::Kernel namespace contains a suite of functions which are plugged into 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''' which 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.		The POE::Kernel namespace contains a suite of functions which are plugged into 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''' which 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'''.		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'''.

	:NOTE: As the Perl tradition mandates, POE is also a moving target.		:NOTE: As the Perl tradition mandates, POE is also a moving target.

	Always check [[CPAN]] to see what new goodies the community has placed in the archive.		Always check [[CPAN]] to see what new goodies the community has placed in the archive.

Vladimir Alexiev: fix link to event loop

2024-09-06T11:38:09Z

fix link to event loop

← Previous revision		Revision as of 11:38, 6 September 2024
Line 9:		Line 9:

	From CPAN:		From CPAN:
	:''"POE originally was developed as the core of a persistent object server and runtime environment. It has evolved into a general purpose multitasking and networking framework, encompassing and providing a consistent interface to other ~~event~~ [[~~Program~~ ~~loops\|loops~~]] such as Event and the [[Tk (software)\|Tk]] and [[GTK\|Gtk]] toolkits."''		:''"POE originally was developed as the core of a persistent object server and runtime environment. It has evolved into a general purpose multitasking and networking framework, encompassing and providing a consistent interface to other [[event loop]]s such as Event and the [[Tk (software)\|Tk]] and [[GTK\|Gtk]] toolkits."''

	==Architecture and layers of abstraction ==		==Architecture and layers of abstraction ==

Doomhope: converted section titles to lowercase

2024-05-31T06:34:16Z

converted section titles to lowercase

← Previous revision		Revision as of 06:34, 31 May 2024
Line 11:		Line 11:
	:''"POE originally was developed as the core of a persistent object server and runtime environment. It has evolved into a general purpose multitasking and networking framework, encompassing and providing a consistent interface to other event [[Program loops\|loops]] such as Event and the [[Tk (software)\|Tk]] and [[GTK\|Gtk]] toolkits."''		:''"POE originally was developed as the core of a persistent object server and runtime environment. It has evolved into a general purpose multitasking and networking framework, encompassing and providing a consistent interface to other event [[Program loops\|loops]] such as Event and the [[Tk (software)\|Tk]] and [[GTK\|Gtk]] toolkits."''

	==~~POE~~ Architecture: ~~Layers~~ of ~~Abstraction~~ ==		==Architecture and layers of abstraction ==
	POE, The '''Perl Object Environment''' can be thought of as a tiny modular [[operating system]]. One or more POE programs or instances can be run concurrently and are generally well suited for [[cooperative multitasking]]. The POE package consists of [[namespace]]s and [[Abstraction (computer science)\|abstractions]] that guide future development of POE in an open-ended [[CPAN\|CPAN-style]] convention.		POE, The '''Perl Object Environment''' can be thought of as a tiny modular [[operating system]]. One or more POE programs or instances can be run concurrently and are generally well suited for [[cooperative multitasking]]. The POE package consists of [[namespace]]s and [[Abstraction (computer science)\|abstractions]] that guide future development of POE in an open-ended [[CPAN\|CPAN-style]] convention.

Line 30:		Line 30:
	A more featureful [[event handler]] is a POE::Session subclass called '''POE::NFA''' - an event-driven [[Nondeterministic finite automaton]] (a ''smarter'' finite state machine). This event handler moves from one strictly defined state to another as events, polls, user selections, or other external events require. This [[finite-state machine\|state machine]] acts to encapsulate a wide range of generic [[Event-driven programming\|event driven]] [[thread (computing)\|threads]] allowing much tighter tracking along the [[execution path]] than the relatively informal POE::Session.		A more featureful [[event handler]] is a POE::Session subclass called '''POE::NFA''' - an event-driven [[Nondeterministic finite automaton]] (a ''smarter'' finite state machine). This event handler moves from one strictly defined state to another as events, polls, user selections, or other external events require. This [[finite-state machine\|state machine]] acts to encapsulate a wide range of generic [[Event-driven programming\|event driven]] [[thread (computing)\|threads]] allowing much tighter tracking along the [[execution path]] than the relatively informal POE::Session.

	===The I/O ~~Layer~~===		===The I/O layer===
	The Kernel's next requirement is for Input-Output handlers that exist in a single I/O layer called ''Wheels''. Wheels initiate actions, handle their resulting low-level events, and produce higher-level events for the sessions that use them. Wheels, like Sessions and Loops are built from a uniform set of abstractions - '''POE::Wheel''' - that sit on top of the Kernel. There are seven highly specialized and well-defined Wheels in POE's base distribution:		The Kernel's next requirement is for Input-Output handlers that exist in a single I/O layer called ''Wheels''. Wheels initiate actions, handle their resulting low-level events, and produce higher-level events for the sessions that use them. Wheels, like Sessions and Loops are built from a uniform set of abstractions - '''POE::Wheel''' - that sit on top of the Kernel. There are seven highly specialized and well-defined Wheels in POE's base distribution:
	*POE::Wheel::Run - Creates and interacts with child processes using pipe(), fork(), and sometimes exec(). Interaction is done through the child's standard input and output.		*POE::Wheel::Run - Creates and interacts with child processes using pipe(), fork(), and sometimes exec(). Interaction is done through the child's standard input and output.
Line 54:		Line 54:
	see [http://metacpan.org/module/POE POE at CPAN] for the complete list		see [http://metacpan.org/module/POE POE at CPAN] for the complete list

	==~~POE~~ Components==		==Components==
	Several larger [[Modular programming\|packages]] have been written in POE according to the '''POE::Component''' documentation. These are event-driven modules, many of which act as little [[Daemon (computing)\|daemons]] that provide services to larger packages to which they belong. Some of them facilitate higher-level communications between modules, especially stand-alone applications that need to remain independent from the main distribution of Perl.		Several larger [[Modular programming\|packages]] have been written in POE according to the '''POE::Component''' documentation. These are event-driven modules, many of which act as little [[Daemon (computing)\|daemons]] that provide services to larger packages to which they belong. Some of them facilitate higher-level communications between modules, especially stand-alone applications that need to remain independent from the main distribution of Perl.

Line 68:		Line 68:
	This should be true for any library, though."		This should be true for any library, though."

	==~~POE~~ Humor==		==Humor==
	* The Acme::POE::Knee module on the [[CPAN]].		* The Acme::POE::Knee module on the [[CPAN]].
	* A number of silly acronym expansions at the end of What POE Is.		* A number of silly acronym expansions at the end of What POE Is.

Doomhope: added short description

2024-05-31T06:32:29Z

added short description

← Previous revision		Revision as of 06:32, 31 May 2024
Line 1:		Line 1:
			{{Short description\|Library of modules (software)}}
	{{For\|the Mach variant\|Mach (kernel)}}		{{For\|the Mach variant\|Mach (kernel)}}
	{{Multiple issues\|		{{Multiple issues\|

Widefox: /* top */ fix sect WP:ORDER, fix hatnote, def acro per MOS

2024-01-01T15:17:17Z

top: fix sect WP:ORDER, fix hatnote, def acro per MOS

← Previous revision		Revision as of 15:17, 1 January 2024
Line 1:		Line 1:
		⚫	{{For\|the Mach variant\|Mach (kernel)}}
	{{Multiple issues\|		{{Multiple issues\|
	{{essay-like\|date=October 2018}}		{{essay-like\|date=October 2018}}
Line 4:		Line 5:
	{{manual\|article\|date=January 2017}}		{{manual\|article\|date=January 2017}}
	}}		}}
		⚫	The '''Perl Object Environment''' ('''POE''') is a [[library (computing)\|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.
⚫	~~: ''~~For the Mach variant~~, see [[~~Mach (kernel)~~]]''~~

⚫	The '''Perl Object Environment''' or '''POE''' is a [[~~Library~~ (computing)\|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.

	From CPAN:		From CPAN:

Bumm13: /* The I/O Layer */ formatting fix

2023-03-12T01:58:28Z

The I/O Layer: formatting fix

← Previous revision		Revision as of 01:58, 12 March 2023
Line 38:		Line 38:
	*POE::Wheel::ListenAccept - A subset of POE::Wheel::SocketFactory used for listening on existing server sockets and accepting connections from remote clients.		*POE::Wheel::ListenAccept - A subset of POE::Wheel::SocketFactory used for listening on existing server sockets and accepting connections from remote clients.
	*POE::Wheel::ReadLine - A non-blocking, event driven analogue to Term::ReadLine.		*POE::Wheel::ReadLine - A non-blocking, event driven analogue to Term::ReadLine.
	*POE::Wheel::ReadWrite - A high-performance [[Asynchronous I/O\|NBIO]] file handler for POE that uses POE's ''[[~~software~~ driver\|~~driver~~]]s'' and ''[[filter (software)\|filter]]s'' to perform buffered read and write on '''[[filehandle]]s''' which draws on the next layer - POE's own little file system.		*POE::Wheel::ReadWrite - A high-performance [[Asynchronous I/O\|NBIO]] file handler for POE that uses POE's ''[[device driver\|drivers]]'' and ''[[filter (software)\|filter]]s'' to perform buffered read and write on '''[[filehandle]]s''' which draws on the next layer - POE's own little file system.

	===The file layers===		===The file layers===

Bumm13: /* POE Components */ formatting fix

2023-03-12T01:57:19Z

POE Components: formatting fix

← Previous revision		Revision as of 01:57, 12 March 2023
Line 55:		Line 55:

	==POE Components==		==POE Components==
	Several larger [[Modular programming\|packages]] have been written in POE according to the '''POE::Component''' documentation. These are event-driven modules, many of which act as little [[Daemon (~~computer software~~)\|daemons]] that provide services to larger packages to which they belong. Some of them facilitate higher-level communications between modules, especially stand-alone applications that need to remain independent from the main distribution of Perl.		Several larger [[Modular programming\|packages]] have been written in POE according to the '''POE::Component''' documentation. These are event-driven modules, many of which act as little [[Daemon (computing)\|daemons]] that provide services to larger packages to which they belong. Some of them facilitate higher-level communications between modules, especially stand-alone applications that need to remain independent from the main distribution of Perl.

	In general, POE Components are ready-made high level procedures that perform specific large tasks. A few examples:		In general, POE Components are ready-made high level procedures that perform specific large tasks. A few examples:

Bumm13: /* The event layer */ punctuation and formatting fixes

2023-03-12T01:56:30Z

The event layer: punctuation and formatting fixes

← Previous revision		Revision as of 01:56, 12 March 2023
Line 26:		Line 26:
	(...and remember Perl's Motto: "There's more than one way to do it" per [[Larry Wall\|Larry]])		(...and remember Perl's Motto: "There's more than one way to do it" per [[Larry Wall\|Larry]])

	The Running Kernel operates through primordial [[finite state machine]]s constructed from another set of abstractions ruled by the '''POE::Session''' architecture. A POE::Session is almost trivially defined as a map of events to the functions, class [[Method (computer ~~science~~)\|methods]], and/or object methods that handle them. POE::Session objects also contain a storage space shared by all its event handlers, called a [[heap (programming)\|heap]]. Any way you slice them the states are solidly identified and clearly defined.		The Running Kernel operates through primordial [[finite-state machine]]s constructed from another set of abstractions ruled by the '''POE::Session''' architecture. A POE::Session is almost trivially defined as a map of events to the functions, class [[Method (computer programming)\|methods]], and/or object methods that handle them. POE::Session objects also contain a storage space shared by all its event handlers, called a [[heap (programming)\|heap]]. Any way you slice them the states are solidly identified and clearly defined.

	A more featureful [[event handler]] is a POE::Session subclass called '''POE::NFA''' - an event-driven [[Nondeterministic finite ~~Automaton~~]] (a ''smarter'' finite state machine). This event handler moves from one strictly defined state to another as events, polls, user selections, or other external events require. This [[state machine]] acts to encapsulate a wide range of generic [[Event-driven programming\|event driven]] [[thread (~~computer science~~)\|~~thread~~]]s allowing much tighter tracking along the [[execution path]] than the relatively informal POE::Session.		A more featureful [[event handler]] is a POE::Session subclass called '''POE::NFA''' - an event-driven [[Nondeterministic finite automaton]] (a ''smarter'' finite state machine). This event handler moves from one strictly defined state to another as events, polls, user selections, or other external events require. This [[finite-state machine\|state machine]] acts to encapsulate a wide range of generic [[Event-driven programming\|event driven]] [[thread (computing)\|threads]] allowing much tighter tracking along the [[execution path]] than the relatively informal POE::Session.

	===The I/O Layer===		===The I/O Layer===

Bumm13: /* POE Architecture: Layers of Abstraction */ link disambiguation and formatting fixes

2023-03-12T01:54:31Z

POE Architecture: Layers of Abstraction: link disambiguation and formatting fixes

← Previous revision		Revision as of 01:54, 12 March 2023
Line 12:		Line 12:

	==POE Architecture: Layers of Abstraction ==		==POE Architecture: Layers of Abstraction ==
	POE, The '''Perl Object Environment''' can be thought of as a tiny modular [[operating system]]. One or more POE programs or instances can be run concurrently and are generally well suited for [[cooperative multitasking]]. The POE package consists of [[~~namespaces~~]] and [[~~abstraction~~]]s that guide future development of POE in an open-ended [[CPAN\|CPAN-style]] convention.		POE, The '''Perl Object Environment''' can be thought of as a tiny modular [[operating system]]. One or more POE programs or instances can be run concurrently and are generally well suited for [[cooperative multitasking]]. The POE package consists of [[namespace]]s and [[Abstraction (computer science)\|abstractions]] that guide future development of POE in an open-ended [[CPAN\|CPAN-style]] convention.

	===The event layer===		===The event layer===
	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 informal architecture consists of a set of layers with a [[Kernel (operating system)\|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 into 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''' which 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.		The POE::Kernel namespace contains a suite of functions which are plugged into 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''' which 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.

Bumm13: formatting fix

2023-03-12T01:52:56Z

formatting fix

← Previous revision		Revision as of 01:52, 12 March 2023
Line 4:		Line 4:
	{{manual\|article\|date=January 2017}}		{{manual\|article\|date=January 2017}}
	}}		}}
	: ''For the Mach variant, see [[Mach kernel]]''		: ''For the Mach variant, see [[Mach (kernel)]]''

	The '''Perl Object Environment''' or '''POE''' is a [[Library (computing)\|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.		The '''Perl Object Environment''' or '''POE''' is a [[Library (computing)\|library]] of Perl modules written in the [[Perl]] [[programming language]] by [[Rocco Caputo]] et al.

← Previous revision		Revision as of 06:32, 31 May 2024
Line 1:		Line 1:
			{{Short description\|Library of modules (software)}}
	{{For\|the Mach variant\|Mach (kernel)}}		{{For\|the Mach variant\|Mach (kernel)}}
	{{Multiple issues\|		{{Multiple issues\|