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.

Net::Server nightmares 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • At ValueClick we wrote a daemon that started out as "nonforker" from the Perl Cookbook. It has been used for many many billion messages since then without any problems. If your protocol is reasonably linebased and the system can work as a non forking daemon, then maybe I can release the code. (It's from my pre-ValueClick time and we just extended and optimized it (heavily) there).
    --

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();

    • Re:non-forking (Score:2)

      by Matts (1087) on 2002.06.07 13:57 (#9307) Journal
      PPerl isn't line based - it passed the STDIN/STDOUT over the socket byte by byte. And it needs to fork (otherwise there's very little point - I would do it in POE if I didn't need it to work like this).

      On the other hand, I've just "solved" or hacked around the ARGV magic stuff. Not sure why what I did worked, but that's what you get with wierd stuff like I'm trying to pull off.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.