poe::pipe::twoway(3pm) [debian man page]

POE::Pipe::TwoWay(3pm)					User Contributed Perl Documentation				    POE::Pipe::TwoWay(3pm)

NAME

       POE::Pipe::TwoWay - a portable API for two-way pipes

SYNOPSIS

	 my ($a_read, $a_write, $b_read, $b_write) = POE::Pipe::TwoWay->new();
	 die "couldn't create a pipe: $!" unless defined $a_read;

DESCRIPTION

       Pipes are troublesome beasts because there are a few different, incompatible ways to create them, and many operating systems implement some
       subset of them.	Therefore it's impossible to rely on a particular method for their creation.

       POE::Pipe::TwoWay will attempt to create a bidirectional pipe using an appropriate method.  If that fails, it will fall back to some other
       means until success or all methods have been exhausted.	Some operating systems require certain exceptions, which are hardcoded into the
       library.

       The upshot of all this is that an application can use POE::Pipe::TwoWay to create a bidirectional pipe without worrying about the mechanism
       that works in the current run-time environment.

       By the way, POE::Pipe::TwoWay doesn't use POE internally, so it may be used in stand-alone applications without POE.

PUBLIC METHODS

   new [TYPE]
       Create a new two-way pipe, optionally constraining it to a particular TYPE of pipe.  Two-way pipes have two ends, both of which can be read
       from and written to.  Therefore, a successful new() call will return four handles: read and write for one end, and read and write for the
       other.  On failure, new() sets $! to describe the error and returns nothing.

	 my ($a_read, $a_write, $b_read, $b_write) = POE::Pipe::TwoWay->new();
	 die $! unless defined $a_read;

       TYPE may be one of "pipe", "socketpair", or "inet".  When set, POE::Pipe::TwoWay will constrain its search to either "pipe()", a UNIX-
       domain "socketpair()", or plain old sockets, respectively.  Otherwise new() will try each method in order, or a particular method
       predetermined to be the best one for the current operating environment.

BUGS

       POE::Pipe::OneWay may block up to one second on some systems if failure occurs while trying to create "inet" sockets.

SEE ALSO

       POE::Pipe, POE::Pipe::OneWay.

AUTHOR &; COPYRIGHT
       POE::Pipe::TwoWay is copyright 2000-2008 by Rocco Caputo.  All rights reserved.	POE::Pipe::TwoWay is free software; you may redistribute
       it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2012-05-15						    POE::Pipe::TwoWay(3pm)

Check Out this Related Man Page

POE::Resource(3pm)					User Contributed Perl Documentation					POE::Resource(3pm)

NAME

       POE::Resource - internal resource managers for POE::Kernel

SYNOPSIS

       Varies, although most POE::Resource subclasses do not have public APIs.

DESCRIPTION

       POE manages several types of information internally.  Its Resource classes are mix-ins designed to manage those types of information behind
       tidy, mostly private interfaces.  This was done to facilitate testing and a conversion to C without the need to port POE::Kernel all at
       once.

       POE::Resource subclasses are generally different from one another, but there are some similarities to note.

       Every resource should have an initializer and finalizer method.	Initializers set up initial data and link resources into POE::Kernel.
       Finalizers clean up any remaining data and verify that each resource subsystem was left in a consistent state.

       One common theme in resource implementations is that they don't need to perform much error checking, if any.  Resource methods are used
       internally by POE::Kernel and/or POE::API classes, so it's up to them to ensure correct usage.

       Resource methods follow the naming convention _data_???_activity, where ??? is an abbreviation for the type of resource it belongs to:

	 POE::Resource::Events	    _data_ev_initialize
	 POE::Resource::FileHandles _data_handle_initialize
	 POE::Resource::Signals     _data_sig_initialize

       Finalizer methods end in "_finalize".

	 _data_ev_finalize
	 _data_handle_finalize
	 _data_sig_finalize

       Finalizers return true if a resource shut down cleanly, or false if there were inconsistencies or leaks during end-of-run checking.  The
       t/res/*.t tests rely on these return values.

SEE ALSO

       POE::Resource::Aliases, POE::Resource::Events, POE::Resource::Extrefs, POE::Resource::FileHandles, POE::Resource::SIDs,
       POE::Resource::Sessions, POE::Resource::Signals

       Also see "Resources" in POE::Kernel for for public information about POE resources.

BUGS

       None known.

AUTHORS &; LICENSING
       Please see POE for more information about its authors, contributors, and licensing.

perl v5.14.2							    2012-05-15							POE::Resource(3pm)

Linux and UNIX Man Pages

poe::pipe::twoway(3pm) [debian man page]

Check Out this Related Man Page