News for hackers. Stuff that matters.
Re:Introducing Socket.io 1.0 by EGreg on Wednesday May 28, 2014 @04:00PM (#7812461)
someone should do primus vs socket.io

why would I need engine.io,websockets for example when engine.io already uses websockets if it can upgrade the connection to them?

Re:Introducing Socket.io 1.0 by lpinca on Wednesday May 28, 2014 @06:01PM (#7813244)
You can't use both. In Primus you can select only one transformer, listed above by V1, but if something doesn't work, you can just switch it with a single line of code. No rewrites, no need to learn a new API.
Re:Introducing Socket.io 1.0 by EGreg on Wednesday May 28, 2014 @08:36PM (#7813921)
I know you can't use both, but doesn't engine.io already support websockets?
Re:Introducing Socket.io 1.0 by lpinca on Thursday May 29, 2014 @02:45AM (#7815066)
Yes it does, but if you are building something that works perfectly only using websockets (e.g. a command-line utility), why would you use engine.io?

You can tell engine.io to only use websockets, but what's the point if you can use websockets directly and have the same API?