Overriding Webservice Limitation: "one call per second" using a Proxy Server
-
I've read the license agreement for my webservice and specifically note the clause "one call per second per IP address", my question is about "masking" IP addresses. Is it possible to route my webservice calls through a proxy server in combination with multiple worker threads thereby possibly making more than 1 request per second? I've seen this technology before concerning web surfing. There are free proxy servers willing to route your packet traffic, I'm just not sure how to implement something like that. Basically give each thread its own proxy server that can route 1 call per second with the end result being 10 threads means 10 calls per second approxiamately.
-
I've read the license agreement for my webservice and specifically note the clause "one call per second per IP address", my question is about "masking" IP addresses. Is it possible to route my webservice calls through a proxy server in combination with multiple worker threads thereby possibly making more than 1 request per second? I've seen this technology before concerning web surfing. There are free proxy servers willing to route your packet traffic, I'm just not sure how to implement something like that. Basically give each thread its own proxy server that can route 1 call per second with the end result being 10 threads means 10 calls per second approxiamately.
That would be like cheating ... not? - Jake
-
That would be like cheating ... not? - Jake
Why yes it would be, but thats the beauty of it. Any hints?
-
I've read the license agreement for my webservice and specifically note the clause "one call per second per IP address", my question is about "masking" IP addresses. Is it possible to route my webservice calls through a proxy server in combination with multiple worker threads thereby possibly making more than 1 request per second? I've seen this technology before concerning web surfing. There are free proxy servers willing to route your packet traffic, I'm just not sure how to implement something like that. Basically give each thread its own proxy server that can route 1 call per second with the end result being 10 threads means 10 calls per second approxiamately.
So what? You're violating your license agreement with that provider. If they find out what you're doing, you'll be making a maximum of 0 requests per second.
Dave Kreskowiak Microsoft MVP - Visual Basic
-
Why yes it would be, but thats the beauty of it. Any hints?
Hint to do something bordering on illegal? Something that can get you sued? I don't think so...
Dave Kreskowiak Microsoft MVP - Visual Basic
-
I've read the license agreement for my webservice and specifically note the clause "one call per second per IP address", my question is about "masking" IP addresses. Is it possible to route my webservice calls through a proxy server in combination with multiple worker threads thereby possibly making more than 1 request per second? I've seen this technology before concerning web surfing. There are free proxy servers willing to route your packet traffic, I'm just not sure how to implement something like that. Basically give each thread its own proxy server that can route 1 call per second with the end result being 10 threads means 10 calls per second approxiamately.
I am going to answer the technical side of your question: I have done this before. My system consisted of following components: 1.Spider which collects proxy addresses from the web using google search and regex. 2.Proxy server test app. This apps goes thru the list of proxies and makes calls to webservice on my server using those proxies. This is done to make sure proxy acually works. Here is a good article on this topic http://www.codeproject.com/vb/net/web\_service\_by\_proxy.asp 3.A webservice which serves up valid proxy addresses. -- modified at 16:02 Thursday 17th August, 2006