Sundial Services <in**@sundialservices.com> wrote in message news:<co**********@domitilla.aioe.org>...
<snip>
If you have to ask... you're contemplating opening /way/ too many processes.
The number of processes that are alive at any one time should be small. You
should /never/ "create a process, let it handle one request and die." The
more runnable processes there are, the less time per-second each process
can receive. If you want to process several requests, use a queue, and
have the children remove requests from that queue.
would an implementation whereby ea. process accessed a single file /
used that file as a queue be sufficient?
although that said, i think for my purposes, multiple processes may be
better (please correct me if i'm wrong). i'm trying to detect whether
or not those attempting to perform a certain action on a website are
doing so from proxies. because it takes about a second to reject a
proxy (well, using 1 as the timeout) it'd take about 8 seconds (if i
wanted to take 8 ports). that's a bit too much time, so i'm using
multiple processes to reduce it to (ideally) a second.