Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • i have a design for a module which will likely do what you want which is threads without perl threads. it will be called Event::ThreadFarm and it will create a farm of kernel/c level threads which interact with a perl level event loop via pipes. operations can be sent to the threads which will run plugins (which come with the module or custom). the perl side will be a callback api which interacts with the rest of the perl process. IO::AIO is a similar module in concept but narrower in scope as it doesn't do plugins and it is tied to one event loop style.

    also stem is a message passing based system in perl which might help you with your apps. it is much higher level than the fork:: and proc:: modules. the cpan version is way out of date but you can get the beta of .11 at stemsystems.com/Stem-0.11.tar.gz.

    when Event::ThreadFarm is out and integrated with stem you will be able to create a message passing framework in a single process that can handle events or dispatch all blocking operations to fast kernel threads. a good combination to look forward to IMNSHO. :)

    uri