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

Support streaming API #22

Open
ZweiSteinSoft opened this issue Jul 2, 2013 · 5 comments
Open

Support streaming API #22

ZweiSteinSoft opened this issue Jul 2, 2013 · 5 comments

Comments

@ZweiSteinSoft
Copy link
Contributor

Streaming API. That means, you call the API server once and get back a continuous stream of data, running as long as you wish. Unfortunately, web browsers today do not fully support the necessary WebSockets API, as you can see on this graph.

@mynetx mynetx modified the milestones: 2.6.0 “Bedale”, 2.5.0 “Altofts” May 24, 2014
@mynetx mynetx modified the milestone: 2.6.0 “Bedale” Sep 30, 2014
@mynetx mynetx modified the milestone: 3.0 “Calverley” Apr 6, 2015
@mynetx
Copy link
Member

mynetx commented Dec 4, 2015

Twitter does not support HTML5 WebSockets. Implementing this is only possible with a server-side Node.js environment, like with sockets.io.

Pushing this back to a later release thus. For now, please take a look at https://github.com/andregoncalves/twitter-nodejs-websocket.

@mynetx mynetx removed this from the 3.0 “Calverley” milestone Dec 4, 2015
@mynetx
Copy link
Member

mynetx commented Dec 4, 2015

bildschirmfoto 2015-12-04 um 19 41 41

@ahanriat
Copy link

Looks like it is now well supported 👀 🆙

@mynetx
Copy link
Member

mynetx commented Jan 22, 2017

@ahanriat Can you post a sample please?

@ahanriat
Copy link

@jublo Sorry I think my message was a bit ambiguous, I was talking about the websocket support, nnd it is now well supported http://caniuse.com/#feat=websockets 😃

@dkzeb dkzeb mentioned this issue Mar 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants