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