Closed jsha closed 9 years ago
Right now stream.js immediately reconnects, potentially getting in a loop. Instead it should respect the 420 status code and back off: https://dev.twitter.com/streaming/overview/connecting
420 was already handled, but there were some other cases where there wasn't enough backoff, now fixed.
Right now stream.js immediately reconnects, potentially getting in a loop. Instead it should respect the 420 status code and back off: https://dev.twitter.com/streaming/overview/connecting