You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
apparently the close (or end for that matter) event is not fired on some occasions.
If I have one client connecting the to stream action and I fire up another client with same credentials the first one will stop getting the data, but apparently there's no way for me to know through events.
jsjohnst
pushed a commit
to jsjohnst/twitter-node
that referenced
this issue
Mar 18, 2012
Is there an event or something when i can listen for or a way i can make sure that the twitter-node connection get's reset if it gets dropped?
The text was updated successfully, but these errors were encountered: