Timeline for Best strategies for calling the API with full throttling support?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 10, 2012 at 18:16 | comment | added | hippietrail | Yes I would definitely intend to throttle my retries. Some of the things I'm playing with fetches lots of data at the start then the user can browser/manipulate it in various ways that will last a while, so far not needing to use the API further. So I could wait 5 seconds before retrying the lost data since the user could still be using it for a much longer time. | |
| Sep 10, 2012 at 18:12 | comment | added | hippietrail | I ask about simultaneous requests because sometimes you know know the minimum requests you will need, and you could make them all at once to be better for the user, or one at a time to be better to the API. So I guess I want to know if I should try to balance these or always go easy on the API. (One example is getting every page in a list, in my case the tags and tags synonyms lists.) | |
| Sep 10, 2012 at 17:45 | history | answered | Kevin Montrose | CC BY-SA 3.0 |