When I call the start-filtering method all goes well initially, but if the stream is inactive for a bit (around 30 seconds), i.e. no tweets about this particular user are coming down the pike, the following error occurs:
I assumed that twitter would keep the stream open indefinitely. I'm looking through the twitter-api code to see what I'm missing, but I thought I'd post here to see if anyone else has seen this exception before.
Sorry, just noticed this is still open. I think it's because the twitter servers send CR's every 30s which would confuse the json/read-string and make it throw
I'm using code straight from the streaming examples, except I'm filtering on a particular user (oath code not shown):
When I call the start-filtering method all goes well initially, but if the stream is inactive for a bit (around 30 seconds), i.e. no tweets about this particular user are coming down the pike, the following error occurs:
I assumed that twitter would keep the stream open indefinitely. I'm looking through the twitter-api code to see what I'm missing, but I thought I'd post here to see if anyone else has seen this exception before.