Closed treeder closed 12 years ago
This is something different and is entirely client side. Basically if the client receives a 503 response, it should retry with exponential backoff until it gets a different response. A 503 means it wouldn't have made it on the queue yet.
Ahh, makes sense. Ok thanks!
On Sunday, June 24, 2012, Travis Reeder wrote:
This is something different and is entirely client side. Basically if the client receives a 503 response, it should retry with exponential backoff until it gets a different response. A 503 means it wouldn't have made it on the queue yet.
Reply to this email directly or view it on GitHub: https://github.com/iron-io/iron_mq_ruby/issues/9#issuecomment-6535578
It sounds like it already has retry. The readme says it will go back on the queue if not deleted within 10 minutes of the get, right?
Exponential backoff would be a separate issue though.