POE [search.cpan.org] is already a well-established framework for asynchronous (and even synchronous) work with non-blocking (or, with the right code, blocking) I/O behavior.
I've tried to tackle this myself more than once and failed. I think the problem is that as lazy developers, we're used to figuring out the basics pretty quickly and start working with it. POE is different for me (and probably to other developers too). It's not easy to just grab it and start working. It's an intense framework that requires intense studying to understand it. I'm sitting with a notebook and pen (which I haven't done in a long while) and make summaries of the POD files for POE::Kernel [search.cpan.org], POE::Session [search.cpan.org] and a bunch of others in the middle.
Once I'll be able to explain it to myself, I'll sit and write on how to use it, probably here and post it to perlmonks.
Wish me luck. :)
You should contribute it to POE to put up on their web site.
If you're willing to contribute docs to POE, I'd love to include more introductory material in the distribution.
Have you seen this article: http://poe.perl.org/?Evolution_of_a_poe_server
Re:Want to Contribute?
xsawyerx on 2008-12-25T08:59:14
I remember reading that article, and going over the examples and getting lost. Was it revised? I don't know, but I'm reading it again now and it's pretty understandable so far.
I reckon I would still be happy (even thrilled) to contribute docs to POE, if there is any place where I can (considering I'm just approaching novice).
