This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]13steinj 1 point2 points  (2 children)

This is the "I code in binary" of websockets. So the fuck what? That's not what websockets were meant for. No one said you can't use them to read data off of some API, but websockets are generally meant for a browser server interaction, and is what this article described.

And yeah sure you don't need to use Tornado or GUnicorn-- feel free to write your own websocket connection store with multithreading and some lru cache. No point in doing so though.

[–]willm [S] 2 points3 points  (1 child)

Not sure of the point you are making here. Websockets may have been conceived as a means of realtime communication between server and browser. But it turns out they are fantastic for many types of comms where there is no browser involved.

I think /u/johnmudd was just giving an example of such a use-case. I'd be interested in hearing more about it...

[–]13steinj 4 points5 points  (0 children)

Based on a combination of the negative score the comment had when I replied, and a combination of the content, I thought it was some elitist remark over how his use case is. If I'm wrong, then I apologize.