Throttling has no place at all in a Coldfusion app All requests are not equal, a request for one .cfm does not equal another.
Give me a Coldfusion app with a CFTHROTTLE tag and you can crash it in a heart beat, It may cope with well formed requests but throttling, traffic shaping and general application protection has to be done at the right layer and CF server level isn't it. There are well formed requests VS rogue requests to consider By putting a device(read linux box) in front of the server you can monitor the request response time and choose to back off requests accordingly based on the actual performance of your application rather than some notional threshold. I would check out HAProxy which is ideally suited to this type of job or VarnishCache whether or not your interested in the caching facility. My 2p A On 22 August 2011 20:50, Alan Holden <[email protected]> wrote: > There's something called mod_bw that looks promising. > > > > -- > official tag/function reference: http://openbd.org/manual/ > mailing list - > http://groups.google.com/**group/openbd?hl=en<http://groups.google.com/group/openbd?hl=en> > -- Alex Skinner Managing Director Pixl8 Interactive Tel: +448452600726 Email: [email protected] Web: pixl8.co.uk -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
