Alvaro Lopez Ortega wrote:
Diego Giagio wrote:>> Tomorrow I will try to test the patch. I will let you know :-) > > Did you have a chance to test the patch ? Did anyone else test ? I > just want to know whether we are going on the right direction ;) I have been thinking about the current code and the current structure.. Now, the throttler is connection based, but we have to support connections, resources and the server, so I would suggest to change it structure a little bit in order to make it more generic. This is the scheme in my mind. Tell me what you think of it :) Server | +--------|--------+ throttler ------+ | | client | | [Virtual Server] [Thread] throttler ------+ | | client | | [Resources] [Connections] throttler ------+ client Each throttler client stores the information of its context. If we make it generic enough it ought to work in the resource, the virtual server and the server. This object can store the information about the limit, and the information about the current traffic, timing and so on.
...
What do you think of it? It is just an idea :-)
makes a great deal of sense. It does run the risk of significantly slowing down the performance of Cherokee when there are no throttle predicates.
are there different sets of predicates at each chokepoint? are the predicates chained by a full set of logical operations? --- eric _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
