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
Policy for increasing request rate limitation
Moderator: NADEO
Policy for increasing request rate limitation
Please do not PM for support. Instead, create a thread so that everyone can contribute or benefit from the answer!
Re: Policy for increasing request rate limitation
When you say
Nevertheless, the goal is to provide a worflow that is confortable for the developpers, whether they use data services or auth services.
I don't agree. It really depends on the kind of service your offering.why don't separate the OAuth part? On a big site, it is really easy to be at 200 connections in one hour
Nevertheless, the goal is to provide a worflow that is confortable for the developpers, whether they use data services or auth services.
Please do not PM for support. Instead, create a thread so that everyone can contribute or benefit from the answer!
- jonthekiller
- Translator
- Posts: 4702
- Joined: 15 Jun 2010, 11:07
- Manialink: maniaolympics
- Location: In Maniaplanet Alpha
- Contact:
Re: Policy for increasing request rate limitation
Please do not PM for support. Instead, create a thread so that everyone can contribute or benefit from the answer!
Who is online
Users browsing this forum: No registered users and 1 guest