poe::resources(3pm) [debian man page]

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

NAME

       POE::Resources - loader of POE resources

SYNOPSIS

	 # Intended for internal use by POE::Kernel.
	 use POE::Resources;
	 POE::Resources->load();

DESCRIPTION

       POE::Kernel is internally split into different resources that are separately managed by individual mix-in classes.

       POE::Resources is designed as a high-level macro manager for POE::Resource classes.  Currently it implements a single method, load(), which
       loads all the POE::Resource classes.

METHODS

       POE::Resources has a public interface, but it is intended to be used internally by POE::Kernel.	Application programmers should never need
       to use POE::Resources directly.

   load
       POE::Kernel calls load() to loads all the known POE::Resource modules.

       Each resource may be handled by a pure perl module, or by an XS module.	For each resource class, load() first tries to load the
       "POE::XS::Resource::..." version of the module.	If that fails, load() falls back to "POE::Resource::...".

SEE ALSO

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

       See POE::Resource for general discussion about resources and the classes that manage them.

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

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

POE::Driver::SysRW(3pm) 				User Contributed Perl Documentation				   POE::Driver::SysRW(3pm)

NAME

       POE::Driver::SysRW - buffered, non-blocking I/O using sysread and syswrite

SYNOPSIS

       "SYNOPSIS" in POE::Driver illustrates how the interface works.  This module is merely one implementation.

DESCRIPTION

       This driver implements POE::Driver using sysread and syswrite.

PUBLIC METHODS

       POE::Driver::SysRW introduces some additional features not covered in the base interface.

   new [BlockSize => OCTETS]
       new() creates a new buffered I/O driver that uses sysread() to read data from a handle and syswrite() to flush data to that handle.  The
       constructor accepts one optional named parameter, "BlockSize", which indicates the maximum number of OCTETS that will be read at one time.

       "BlockSize" is 64 kilobytes (65536 octets) by default.  Higher values may improve performance in streaming applications, but the trade-off
       is a lower event granularity and increased resident memory usage.

       Lower "BlockSize" values reduce memory consumption somewhat with corresponding throughput penalties.

	 my $driver = POE::Driver::SysRW->new;

	 my $driver = POE::Driver::SysRW->new( BlockSize => $block_size );

       Drivers are commonly instantiated within POE::Wheel constructor calls:

	 $_[HEAP]{wheel} = POE::Wheel::ReadWrite->new(
	   InputHandle => *STDIN,
	   OutputHandle => *STDOUT,
	   Driver => POE::Driver::SysRW->new(),
	   Filter => POE::Filter::Line->new(),
	 );

       Applications almost always use POE::Driver::SysRW, so POE::Wheel objects almost always will create their own if no Driver is specified.

   All Other Methods
       POE::Driver::SysRW documents the abstract interface documented in POE::Driver.  Please see POE::Driver for more details about the following
       methods:

       flush
       get
       get_out_messages_buffered
       put

SEE ALSO

       POE::Driver, POE::Wheel.

       Also see the SEE ALSO section of POE, which contains a brief roadmap of POE's documentation.

AUTHORS &; COPYRIGHTS
       Please see POE for more information about authors and contributors.

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