After encountering a throttle violation today (which I posted in another question), it occurred to me that although I've put together code to handle "backoff" conditions, and potentially throttle violation conditions (although I'm not sure what the response for this is, even) it would be nice to be able to generate these in a controlled fashion.
Does something like this exist? I'd want to be able to do something like:
Which would return a response containing a 30 second backoff request. If I violate it, it would return some error condition. This way I could make sure my implementation of the API calls handles this in a sane/acceptable fashion without violating the backoff condition. Not passing a time might cause a random backoff representing an "average" backoff.
Which would always return a throttle condition, regardless of the current state of my key. That way I could make sure I handle this situation in whatever way is appropriate.
I'm sure there's other things that would be of use for debugging, but offhand these two come to mind.
backoffparameter. My connection has way too much latency I think.