On Mon, 29 Nov 2004, Stas Bekman wrote:
nuke it?
So this is incorrect?
- The MPM does not set a SIGALRM handler, user code may use SIGALRM.
It can use it if it knows what it's doing.
What do you mean?
A mod_perl module that's expected to work on any MPM (which is I'm assuming what you're talking about) is not going to fall into the category of "knows what it's doing" if it tries to use signals. :-)
It's the case with any other mod_*, not only mod_perl.
What the alternative solution for the widely used alarm() technique?
I'd expect to have a documented API, regarding signals in Apache 2.x
* No signals are to be used in user code
* Certain signals (please list which) can be used in all mpms
* Certain signals (please list which) can be used only in certain mpms.
The current situation of guess what works and what will continue to work tomorrow approach sucks.
Let's polish this issue and I'll make sure it's properly documented.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
