Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

moosex::poe::meta::trait::object(3pm) [debian man page]

MooseX::POE::Meta::Trait::Object(3pm)			User Contributed Perl Documentation		     MooseX::POE::Meta::Trait::Object(3pm)

NAME

       MooseX::POE::Meta::Trait::Object - The base class role for MooseX::POE

VERSION

       version 0.215

SYNOPSIS

	   package Counter;
	   use MooseX::Poe;

	   has name => (
	       isa     => 'Str',
	       is      => 'rw',
	       default => sub { 'Foo ' },
	   );

	   has count => (
	       isa     => 'Int',
	       is      => 'rw',
	       lazy    => 1,
	       default => sub { 0 },
	   );

	   sub START {
	       my ($self) = @_;
	       $self->yield('increment');
	   }

	   sub increment {
	       my ($self) = @_;
	       $self->count( $self->count + 1 );
	       $self->yield('increment') unless $self->count > 3;
	   }

	   no MooseX::Poe;

DESCRIPTION

       MooseX::POE::Meta::TraitObject is a role that is applied to the object base classe (usually Moose::Object) that implements a POE::Session.

METHODS

   get_session_id
       Get the internal POE Session ID, this is useful to hand to other POE aware functions.

   yield
   call
   delay
   alarm
   alarm_add
   delay_add
   alarm_set
   alarm_adjust
   alarm_remove
   alarm_remove_all
   delay_set
   delay_adjust
       A cheap alias for the same POE::Kernel function which will gurantee posting to the object's session.

   STARTALL
       Along similar lines to Moose's "BUILDALL" method which calls all the "BUILD" methods, this function will call all the "START" methods in
       your inheritance hierarchy automatically when POE first runs your session. (This corresponds to the "_start" event from POE.)

   STOPALL
       Along similar lines to "STARTALL", but for "STOP" instead.

   START
   STOP
   DEFAULT
   CHILD
   PARENT
DEFAULT METHODS

PREDEFINED EVENTS

AUTHORS

       o   Chris Prather <chris@prather.org>

       o   Ash Berlin <ash@cpan.org>

       o   Chris Williams <chris@bingosnet.co.uk>

       o   Yuval (nothingmuch) Kogman

       o   Torsten Raudssus <torsten@raudssus.de> <http://www.raudssus.de/>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2010 by Chris Prather, Ash Berlin, Chris Williams, Yuval Kogman, Torsten Raudssus.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-04-25				     MooseX::POE::Meta::Trait::Object(3pm)

Check Out this Related Man Page

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)
Man Page