News for hackers. Stuff that matters.

A comment on Introducing Socket.io 1.0. Parent comment

Re:Introducing Socket.io 1.0 by srpeck on Wednesday May 28, 2014 @03:32PM (#7812287)
I looked for a library for a similar WebRTC project. All of the libraries I found contained superfluous functionality, as I was only interested in data channels and did not want to be locked in by a particular third party. I ended up rolling my own; the WebRTC API is simple enough [1] and there is some example code from Google that points the right direction [2]. Additionally, Socket.io makes for a convenient signalling server prototype, though it is overkill.

[1] http://dev.w3.org/2011/webrtc/editor/webrtc.html

[2] https://bitbucket.org/webrtc/codelab

[ Parent | on HN ]
Re:Introducing Socket.io 1.0 by samdutton on Monday June 02, 2014 @05:45AM (#7832649)
You might also find something useful at http://bit.ly/webrtcwebaudio. PeerJS is a library oriented to data exchange: http://peerjs.com.
[ Parent | on HN ]
Re:Introducing Socket.io 1.0 by spb on Thursday May 29, 2014 @11:55PM (#7820186)
If you want a simpler signaling server for WebRTC, you might check out the "caress" server I developed for Chatphrase: http://github.com/chatphrase/caress
[ Parent | on HN ]