Steam Web API server irregularities desperately call for better, long-term "caching"
smiley opened this issue · 1 comments
Today, the Steam Web API experienced some serious outage. Requests took as long as 20 seconds and multiple retransmissions throughout the connection to complete, severely crippling any interactivity this library usually provides.
This signals a need for full serialization and support for "offline objects", meaning Steam API objects which either don't automatically request data from the server, or request it asynchronously and return the old data in the meantime.
This also means gevent should be looked into again as an asynchronous solution, since requests natively supports it for async requests.
A lot has changed since then, and the Steam web API has improved tremendously. The longest RTT I've seen is 2 seconds, from Europe with an Amazon API Gateway (mine) in-between. I think this can be considered resolved. If the API starts messing up regularly again, I'll reopen this.