In a current endeavor, I am starting to use POE. Admittedly, it's because I don't feel like writing a state machine plus a server; however, it appears that POE seems to make this a bit easier by providing a framework. Of course, it feels a bit like wrapping oneself around MPW, Metrowerks, RogueWave, or MFC, but still it's a decent framework.

I am curious as to the performance of the beastie in a production environment, as opposed to writing a simpler graph used as a callback table, triggered on transitions, vis-a-vis NerveCenter et al.

I do believe that writing drop-in components will become easier once I write a more generic Component loader -- or at least settle on a well-defined directory/folder structure for the packages --, since to achieve such ease of extensibility, the Component/Filter/Wheel paradigm must evolve to a new abstraction, such as a generic plug-in with a set directory OR package structure. Just as we tend to write -- or some variant thereof -- ... 

pacakge Foo;

sub new {
  my $this = shift;
  my $class = ref($this) || $this;
  my $self = {};
  bless $self, $class;
  return $self;
}

1;

[download]
...so too will we see the likes in POE.

-v
"Perl. There is no substitute."

In reply to Re^2: Show me the missing Big Deal of POE. by Velaki
in thread Show me the missing Big Deal of POE. by swiftone

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.