Make core.rtcpeerconnection / core.rtcdatachannel exist

[willscott]

likely via http://js-platform.github.io/node-webrtc/

[willscott]

wrtc is included as an optional dependency.

[willscott]

Discussion towards a sane server-side webRTC setup is beginning here: webrtcftw/goals#1

[modeswitch]

@willscott What are your thoughts about media streams? I'm seriously considering removing that as a goal for node-webrtc given the difficulty in building libjingle for most people. I've made good progress on thinning out libjingle and I should have a new build of node-webrtc that is data-channels only.

[willscott]

@modeswitch fantastic! Media streams & Codec compatibility seems like the heavy part of the library, and it would be great to separate out the connection negotiation & data channel APIs from the audio/video stuff.

Looking forwards to a thinned out library!

[modeswitch]

@willscott Unfortunately, adding media support back in as a module of some sort will be difficult. I wonder if it would make more sense to proxy media streams (on the browser side) over data channels, and just dump the media/codec code from the node-side altogether.

[willscott]

@modeswitch I'd be happy to just have working data channels on node for now!

As soon as you have something that it would be useful to have testers on, let me know and I'm happy to start playing with it & filing bugs against it 👍

[ryscheng]

👍

[agallant]

Taking this as a renewed priority for getting uProxy-for-cloud running in node rather than Docker images with Firefox (thus hopefully improving setup time, performance, etc. etc.).

[agallant]

Some notes - node-wrtc has some build issues on OSX, node-webrtc/node-webrtc#235 (comment)

May still go with it, but I'm also looking into other fill options. One that I'm not sure if it's appropriate, but may be convenient if so - https://github.com/mappum/electron-webrtc

[agallant]

It exists now (w/caveat that building currently requires Linux rather than OSX due to dependency) - #40