barmar, on 2013-October-11, 09:31, said:
I'm not sure quite what you're asking. Bringing up your results for a single tourney or for a time range is one request, and then each time you click on "Traveller" it's another request.
We've increased the threshold in the rate limiting. If you send the requests 5 seconds apart, you should be OK. This means that downloading 15 results will take a little over a minute. Sorry for the inconvenience.
I see that we agree that clicking on a link or query from excel are the same.
But I want to remind that there are two types of queries.
The first may be called rapid. Through "recent tournaments", we want to see the results of the tournament , or take a look at the tables in a particular board. When we ask server we usually get data on our browser immediately. In Poland or in India. But the distance isn't short. How is this possible ? BBo server knows tournament number board number and is already sending data . I think that he is able to handle 10,000 such requests per second . But do not be surprised for me it was 1,000,000 .
But there are slow queries yet type "username =" of Myhands . Enter nickname, one month and begin to count... 121, 122 , 123 got results ! This means that the query costs 30,000 times more !
Request type "username =" is expensive even for two days requires much more work the server!
I think if someone was able to delay the server so only through slow queries. This type of query can be restricted !
Generally. First detection then restrictions. Not vice versa.
Withdraw please!