Re: [htdig-dev] server_wait_time directive

[Geoff H. <ghu...@ws...>]

> I'd rather vote for ignoring it when pcs are on. Or maybe as Geoff 
> says, after the max requests in a row are reached.

No one else seems to have much opinion on this matter. But as I said 
before, I think if server_wait_time is set, you *should* wait at some 
point. To me, it makes logical sense that if the user has set 
max_connection_requests, then we should follow that and wait afterwards. 
If we *never* wait when persistent connections are enabled, we won't be 
good network citizens and won't enable ourselves to "throttle back" on a 
webserver.

In a multiple-server context, there will be at least *some* wait while 
htdig switches to the next server after max_connection_requests. I feel 
that enabling server_wait_time at this point is consistent and will 
prevent server melt-down.

-Geoff