Charles Randall wrote:
> You may want to look at the Zeus server to understand the features
> that were product-worthy as one example. It appears that they've only
> implemented this at the virtual server level.
Good suggestion.. I don't think it'll be any harder with my current
model to implement limits for directories, users, hosts, etc than it
would be for just vhosts, though, so I'm not planning on limiting things
unnecessarily (besides, part of what I really want for my own use are
limits per directory and/or location)..
>As you're probably aware, thttpd also provides flexible bandwidth
>throttling,
>
>http://www.acme.com/software/thttpd/thttpd_man.html#THROTTLING
Actually, no I wasn't, so thanks for the pointer. I'll definitely look
at what they're doing. At first brief glance it looks like what I've
got already is probably slightly more flexible, tho.
Ian Holsman wrote:
> you may want to contact the writers of the apache 1.3 module
> (mod_bandwidth) and see what they are doing.
> (http://www.cohprog.com/mod_bandwidth.html)
> there is also a mod_throttle I think.
Yeah, I've already looked at both mod_bandwidth and mod_throttle.
mod_throttle (if I remember right) just inserts pauses between requests,
so it's not the sort of thing I'm interested in anyway. mod_bandwidth
does have actual rate-limiting, but their rate-per-request calculations
appear to produce some odd results in many cases, and because it's
implemented as a content handler, it can't be used with CGIs,
server-parsed content, etc, so it won't work well for a lot of things.
You're right that I should check with the authors to see if they're
working on anything for 2.0, tho. I'll do that.
-alex
