You could implement the Chain of Responsibility design pattern by promoting ARG0 from an input string to a data structure that includes the input and the steps to process it.

First define a subroutine to pass the job to the next step in the recipe: 

sub what_next {
  my ($kernel, $job) = @_;
  my $next_step = shift @{ $job->{recipe} };
  if (defined $next_step) {
    $kernel->yield( $next_step => $job );
  }
  else {
    $kernel->yield( 'process_next_input' );
  }
}

[download]

process_next_input() builds the job and the initial recipe, and then uses what_next() to start the process: 

sub process_next_input {
  ...;

  my $job = {
    input => $next_input,
    recipe => [ 'step_one', 'step_two' ],
  };

  what_next($_[KERNEL], $job);
}

[download]

All stages of the process end by calling what_next() to pass the work on. You could get fancy by pushing coderefs onto the recipe that conditionally return the next event in the chain.

Sorry for not responding in so long. I'm doing PerlMonks wrong, and I don't notice my message inbox until I actively return to the site. If there's some sort of RSS-like way to check for messages, that would help a lot.

--
Rocco Caputo - http://poe.perl.org/ - irc://irc.perl.org/poe

In reply to Re^3: POE::Wheel::ReadWrite: "low priority" events by rcaputo
in thread POE::Wheel::ReadWrite: "low priority" events by vlad_s

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.