httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dean gaudet <>
Subject Re: Alarms/timeouts in 1.3.x
Date Thu, 20 Apr 2000 23:19:22 GMT
On Thu, 20 Apr 2000, Tom Harrington wrote:

> I know everyone's focused on 2.0, but hopefully someone can help out
> a guy still trying to get 1.3.x running on a new OS...
> We don't have Unix-style signals on this OS, so the use of SIGALRM and
> the Unix version of ap_set_callback_and_alarm is right out for us.
> It looks like what I want to do is #define OPTIMIZE_TIMEOUTS for this
> platform, and then #ifdef out the child_timeouts-related stuff (since
> I don't plan on supporting child_timeouts anyway).

if you don't have signals i don't see how optimize_timeouts would work --
all that does is send the SIGALRM from the parent rather than from the

>  But I notice that
> neither Win32 nor Netware used this approach, even though it seems like
> it would have worked for them.  Is this approach one that I'm likely to
> regret?

they use the same approach we use in 2.0 for all architectures --
individual timeouts on each i/o operation.  look in main/buff.c.


View raw message