Timeline for Request Throttling Limits
Current License: CC BY-SA 2.5
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 31, 2010 at 1:05 | history | edited | Sky Sanders | CC BY-SA 2.5 |
deleted 11966 characters in body
|
| Jul 29, 2010 at 23:54 | comment | added | Steffen Opel | [... continued] The responsiveness of the Stack Exchange team leaves much to be desired though, and I fail to understand what's so hard about saying We'll look into this later at least. This is indeed a major impediment from a professional perspective and does apply to non technical issues as well, see here for an example: again a user (me) is even willing to invest a considerable amount of time eventually to work around a limitation of the API, just like code poet here, but I'm getting ignored and am unable to proceed in good faith therefore! | |
| Jul 29, 2010 at 23:54 | comment | added | Steffen Opel | @jjnguy - I'm glad there is already some agreement here, but to put @code poets engagement into perspective I'd like to add that I don't think his language is condescending (I'm not a native speaker though) and I'm definitely having problems with this and similar issues as well. Code has tackled an enormous amount of issues and gone to great length to work around various existing problems better addressed at the API level already to save others the effort. The least we could expect is to get some timely acknowledgment for issues almost always raised politely and in good faith. [continued ...] | |
| Jul 29, 2010 at 16:27 | comment | added | Sky Sanders | @jjn - see update for some context as to why I am so intent on having unambiguous specifications. | |
| Jul 29, 2010 at 16:26 | history | edited | Sky Sanders | CC BY-SA 2.5 |
added 421 characters in body
|
| Jul 29, 2010 at 15:16 | comment | added | Sky Sanders | i am not the person to ask, @jjn. this information must come from a representative of SO. you and i can wax poetic and postulate ad infinitum but it is nothing more than entertainment. | |
| Jul 29, 2010 at 15:06 | comment | added | jjnguy | I see where the ambiguity lies. Does it mean that any call to a route will count towards the total, or will it count 5/30 for each route separately? | |
| Jul 29, 2010 at 15:03 | comment | added | Sky Sanders | i appreciate your feedback, @jjn, but i have read it carefully and while it certainly may be interpreted as you say, it could also be seen to imply that a request to any single endpoint can count towards your 6ps quota. are you picking up on what i am putting down? there are people courting investors for technology based on the data api and it is things like this that leave far too much to chance. you might want to shift your perspective a bit to understand how my initial attempts to get codification failed and resulted in this post. check the timelines. | |
| Jul 29, 2010 at 14:54 | comment | added | jjnguy | (To be fair, that was only added yesterday, and now I have to re-do my throttling code...) | |
| Jul 29, 2010 at 14:51 | comment | added | jjnguy |
Read this quote carefully: "The API will cut you off if you make more than 30 requests over 5 seconds to any single endpoint." So, your api can make N * 6 requests per second. Where N is the number of routes. This assumes you are spreading your requests equally over each endpoint.
|
|
| Jul 29, 2010 at 14:50 | comment | added | jjnguy | @code, I think the language you use is very condescending. I feel like you are talking above everyone else. No one else seems to have problems with this. | |
| Jul 29, 2010 at 8:29 | history | edited | Sky Sanders | CC BY-SA 2.5 |
added 11930 characters in body; deleted 5 characters in body; deleted 119 characters in body
|
| Jul 29, 2010 at 6:28 | history | answered | Sky Sanders | CC BY-SA 2.5 |