Basically I am just wondering if this is even possible, since I was debugging some code running my app while the user I designed it for was also running it and it caused things to just fail
I am using Ruby’s TweetStream gem to accomplish the functionality. I noticed that when I was trying to refactor some code while the user was testing its functionallity to ensure that it functioned correctly , that the event machine running the code would essentially orphan the stream object and hang in an endless loop. I couldn’t find any documentation explaining why it would do so with the TweetStream gem, so I’m wondering if opening a new stream using the same consumer key, key token, and OAuth key and token is causing twitter to forcibly close the stream for the least recent person to connect.
I haven’t found anything that explicitly says that this will happen but it leads me to believe that it is either an issue with using the same credentials, or that there was an issue with Twitters Streaming API in general tonight. Considering though, that the program appears to work fine when we aren’t trying to run the program at the same time it leads me to believe the first to be the issue