I can't think of any current problems with exit. There used to be a bug
involving exit, but that was fixed.
If you're doing CGI programming with fork and starting something that will
continue running in the background, then you have to be careful to close your
files. This is more a CGI guideline though, because it's true for both perl
and PersistentPerl.
http://www.ssc.com/websmith/issues/i6/ws107.html
If you use the Group option, then all scripts in a group will share
global signal handler settings, becaue they all run in the same process.
But if you set up your signal handlers on each run (instead of setting
them in a BEGIN), then you're probably OK . If you don't use groups
(Group option is set to "none"), then there shouldn't be any special
requirements for signal handlers.
> Hi all,
>
> When coding or porting a program to play nicely with Persistent Perl (aka SpeedyCGI), is there anything special that needs to be done when one uses exit, fork, or a signal handler? FastCGI and mod_perl seem to require you to do special things so the programs work correctly, but the webpage for Persistent Perl doesn't really mention anything special.
>
> Thanks,
> Kevin
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open!
> Get cracking and register here for some mind boggling fun and
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> Persistentperl-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/persistentperl-users
>
|
