On Sun, 2005-02-06 at 23:28 -0800, Pratik wrote:
> -It does all important operations inside PerlLogHandler.
>
> -For my requirements - where the request is serving large files for
> download - I will need to move those operations in higher level
> handlers - Like PerlAccessHandler or PerlInitHandl
On Mon, 07 Feb 2005 06:56:44 -0600, Joseph A Nagy Jr <[EMAIL PROTECTED]> wrote:
> Sounds like you want to disable HTTP Pipelining, am I mistaken? If not,
> Apache already has a mechanism for this, look in the default httpd.conf
> firle 1.3x and 2.x for more info.
Nop. I am not looking to disable H
Pratik wrote:
Hi Everyone !
Currently, I am implementing a mechanism to restrict the number of
parallel connections to the server from a single client/user.
Sounds like you want to disable HTTP Pipelining, am I mistaken? If not,
Apache already has a mechanism for this, look in the default httpd.c
About Stonehenge::Throttle:
-It does all important operations inside PerlLogHandler.
-For my requirements - where the request is serving large files for
download - I will need to move those operations in higher level
handlers - Like PerlAccessHandler or PerlInitHandler.
-In which case, I'd be do
On Sun, 06 Feb 2005 16:40:57 -0500, Perrin Harkins <[EMAIL PROTECTED]> wrote:
> [ Please keep conversation on the list. ]
Oops...sorry for the goof-up. Can't help it :D
> You can store simple +1/-1 values if you want to. The interesting part
> is that it packs the data into a small fixed-size ch
[ Please keep conversation on the list. ]
Pratik wrote:
He is using it to throttle by CPU, but it's easy to make it use number
of connections within a time window instead.
But I am more interested in restricting parallel connections rather
than request/rate.
You can store simple +1/-1 values if yo
Pratik wrote:
I am interested in knowing if I am missing some obvious point here.
This mechanism is working nicely. Are there any better alternatives
available without any overhead of chache/locking etc.
What you're doing sounds fine, but you might be interested in this
approach that Randal demons
Hi Everyone !
Currently, I am implementing a mechanism to restrict the number of
parallel connections to the server from a single client/user.
The mechanis is something like :
- Use Cache::FastMmap to share the data between multiple processes.
- PerlAccessHandler will get the key for cache to g
