[EMAIL PROTECTED] (Randal L. Schwartz) wrote:
>It would be pretty simple, basing it on my CPU-limiting throttle that
>I've published in Linux Magazine
><http://www.stonehenge.com/merlyn/LinuxMag/col17.html>. Just grab a
>flock on the CPU-logging file in the post-read-request phase instead
>of writing to it. If you can't get the flock, reject the request.
>Release the flock by closing the file in the log phase.
>
>But this'd sure mess up my ordinary visit to you, since my browser
>makes 4 connections in parallel to fetch images, and I believe most
>browsers do that these days.
I was thinking about that too, and concluded that you'd only want to
throttle the back-end server in a 2-server setup. That would usually
(save for subrequests) only be 1 request throttled per page-load. I
tend not to care about the front-end, because overload is rarely a
problem there.
------------------- -------------------
Ken Williams Last Bastion of Euclidity
[EMAIL PROTECTED] The Math Forum
