/ 
Reflex-0.072
River stage one • 7 direct dependents • 7 total dependents
/ Reflex::POE::Event

NAME

Reflex::POE::Event - Communicate with POE components expecting events.

VERSION

version 0.072

SYNOPSIS

This BUILD method is from eg-12-poco-event.pl in Reflex's eg directory. It's for an App (application) class that must request service from a POE component by posting an event.

sub BUILD {
  my $self = shift;
  $self->component( PoCoEvent->new() );

  # Make sure it runs within the object's POE::Session.
  $self->run_within_session(
    sub {
      $self->component->request(
        Reflex::POE::Event->new(
          object  => $self,
          method  => "on_component_result",
          context => { cookie => 123 },
        ),
      );
    }
  );
}

App's constructor runs within its creator's session, which may not be the correct one to be sending the event. run_within_session() guarantees that Reflex::POE::Event is sent from the App, so that responses will reach the App later.

An optional context (or continuation) may be stored with the event. It will be returned to the callback as its "context" parameter.

DESCRIPTION

Reflex::POE::Event is a helper object for interacting with POE modules that expect event names for callbacks. It creates an object that may be used as a POE event name. Reflex routes these events to their proper callbacks when POE sends them back.

Authors are encouraged to encapsulate POE interaction within Reflex objects. Most users should not need use Reflex::POE::Event (or other Reflex::POE helpers) directly.

Public Attributes

object

"object" contains a reference to the object that will handle this POE event.

method

"method" contains the name of the method that will handle this event.

context

Context optionally contains a hash reference of named values. This hash reference will be passed to the event's "context" callback parameter.

Callback Parameters

Reflex::POE::Event provides some callback parameters for your convenience.

context

The "context" parameter includes whatever was supplied to the event's constructor. Consider this event and its callback:

my $event = Reflex::POE::Event->new(
	object => $self,
	method => "callback",
	context => { abc => 123 },
);

sub callback {
	my ($self, $args) = @_;
	print(
		"Our context: $args->{context}{abc}\n",
		"POE args: @{$args->{response}}\n"
	);
}

response

POE events often include additional positional parameters in POE's ARG0..$#_ offsets. These are provided as an array reference in the callback's "response" parameter. An example is shown in the documentation for the "context" callback parameter.

CAVEATS

Reflex::POE::Event objects must pass through POE unscathed. POE's basic Kernel and Session do this, but rare third-party modules may stringify or otherwise modify event names. If you encounter one, please let the author know.

Reflex::POE::Event's implementation may change. For example, it may generate strings at a later date, if such strings can fulfill all the needs of the current object-based implementation.

Reflex::POE::Event's interface may change significantly now that we have Reflex::Callbacks. The main change would be to support generic callbacks rather than hardcode for method dispatch.

SEE ALSO

Moose::Manual::Concepts

Reflex Reflex::POE::Postback Reflex::POE::Session Reflex::POE::Wheel::Run Reflex::POE::Wheel

"ACKNOWLEDGEMENTS" in Reflex "ASSISTANCE" in Reflex "AUTHORS" in Reflex "BUGS" in Reflex "BUGS" in Reflex "CONTRIBUTORS" in Reflex "COPYRIGHT" in Reflex "LICENSE" in Reflex "TODO" in Reflex