Page 1 of 1

Policy for increasing request rate limitation

Posted: 15 Feb 2012, 11:43
by gouxim
Fellow coders,

A few asked me about increasing the request rate limit so I thought i'd share our policy on the forum for future reference.

Our policy is not to increase the request rate limit a priori. It allow us to better handle server load ; it also "force" developers to use important best practices such as caching (no need to request the same player object 1000 times per hours ; it's better to cache it for like 1 or 2 hours). Moreover, in my experience, people tend to underestimate this limit.

If however you actually reach the limit (see graph on the API username management page), send me a message with your username: I will check the graph and increase the limit if needed.

QED :ugeek:

Re: Policy for increasing request rate limitation

Posted: 04 Apr 2012, 15:56
by gouxim
When you say
why don't separate the OAuth part? On a big site, it is really easy to be at 200 connections in one hour
I don't agree. It really depends on the kind of service your offering.

Nevertheless, the goal is to provide a worflow that is confortable for the developpers, whether they use data services or auth services.

Re: Policy for increasing request rate limitation

Posted: 27 Jul 2012, 13:29
by jonthekiller
I have seen it's now 600 request per hour :thumbsup:

Re: Policy for increasing request rate limitation

Posted: 27 Jul 2012, 14:38
by gouxim
:yes: