Nearly all, if not all, HTTP error codes returned by the Streaming API
require either human intervention to fix, or waiting many minutes for
a triggered rate limit to cool off. There's little difference in 3xx
codes and the 4xx codes returned, I think you can safely treat them
all equivalently.
R
Thanks for the answer. A follow up: assuming there's no problem with
my code, but I am getting errors opening up a socket due to twitter
updates, acts of god, etc., would this be acceptable behavior (to keep
the socket open):
on > 400 errors: make my retry interval 10 seconds, for the next 4
minu
This would be considered abusive because you are circumventing the per-
connection keyword and rate limits by opening a second connection. The
system may force the first connection to disconnect. If your
application needs to track more keywords or a higher rate than the
default /track level, conta
