Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing track and other stream options #172

Open
unwitting opened this issue Jul 17, 2016 · 5 comments
Open

Changing track and other stream options #172

unwitting opened this issue Jul 17, 2016 · 5 comments
Labels

Comments

@unwitting
Copy link

Given that Twitter only allows a single stream (with multiple parameters) at any one time, what's the advice for changing, say, the track on a stream? Closing the stream and opening a new one with new options, or somehow updating the stream's options while it's alive? If the first, what's a reliable way to kill the connection, and if the second, how?

@enrichman
Copy link

enrichman commented Jul 20, 2016

+1. I'm also interested on this, it should be better documented.

@haddadnidal
Copy link

Me 2.

@gabosdk
Copy link

gabosdk commented Aug 7, 2016

Me 2. Please advise.

@jonas-koeritz
Copy link

jonas-koeritz commented Oct 30, 2016

I will try a request.socket.end() inside the destroy method for streams to explicitly send a FIN packet to Twitter's Server. The current destroy() does not close the connection (at least in my application) and I am receiving DuplicateSteam errors when I try to connect to a new stream. (Which happens quite often, my application switches streams when my TV switches channels). Maybe this could also help on #159?

@dandv
Copy link

dandv commented Dec 21, 2018

This library is no longer maintained.

Here's an example of how to change tracking keywords with twitter-lite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants