On 1/2/08, Marco Marongiu wrote:
I thought that a possible solution could be putting a reverse proxy between the two, so that the proxy accepts and enqueues the requests and forwards them to the service at no more than 10 per second. I had a look at Pound (http://www.apsis.ch/pound/index_html), but it seems it can't do any resource limit on the outbound traffic.
You don't tell us what kind of service you're talking about, but from your mention of Pound, I'm assuming that this is a web problem?
Certainly, setting up a proxy of some sort that can take advantage of connection caching, etc... would seem to be a way to improve your performance, and depending on the nature of the application, I would think that even squid, apache, or other web servers could be set up in this kind of role.
I'm not sure of the exact nature of the application you're talking about, but for example Yahoo! provides some information on setting up a PHP-based proxy for their AJAX web services tools, see <http://developer.yahoo.com/javascript/howto-proxy.html>.
And squid apparently does have a way to limit the number of simultaneous connections from a client, see <http://www.cyberciti.biz/tips/howto-limit-squid-proxy-number-web-connections.html>.
But with just five minutes of Googling, I'm not finding anything else that would appear to be obviously related to what it seems like you're talking about.
-- Brad Knowles <brad@xxxxxxxxxxxxxxxxx> LinkedIn Profile: <http://tinyurl.com/y8kpxu>