Hi,
Alvaro Lopez Ortega wrote:
Hi,
I have been thinking of the bandwidth throttling, and I want to
share my notes with you..
Come on ! :)
Restriction points
==================
- Server: We have to be able to set a bandwidth limit for the whole
server.
- Virtual Server: It is basically the same. Just think of a hosting
scenario. You would want to limit the bandwidth used by a single
client.
- Resources: This is the most interesting one. We want to be able
to set an arbitrary limit to individual resources. I have had
problems before which could be solved easily with this feature.
This restriction point would be used like: "I want to spend 30Kb/s
of my bandwidth to let people download MP3 files, no
more. Otherwise my whole site is going to be down".
That's nice. This will give us a lot of flexibility.
At this moment, our resource management is directory and extension
based, so we should support configuration in those points. (Don't
worry about the implementation, directories and extensions are
*really similar* internally)
In the future, Cherokee will support some more fine grain resource
management. It should not be a problem to make it work in that
scenario though.
Configuration entries
=====================
In my opinion, we need just a configuration reserved word for this.
Something like "Limit" or "Throttle" might works..
I will stick with "Limit" ok? We can easily change this later if we want.
Precedence
==========
We have to find a way to pick up the right limit to a connection.
In my opinion, a precedence is not really needed. We just need to
use the lowest of the limitation values which can affect a
connection.
That's a cleaner, simpler and better approach.
And, by the moment, this is all... ideas? thoughts?
I think your notes are all good and we are going to the right direction.
Diego Giagio
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
