Add support for DataChannels

[piranna]

Add support for DataChannels now that interoperability between Chrome and Firefox is almost ready on Chrome v31, so API is not probably will change on the near future.

[fuson]

I'm really need it too, but looks like this project is dead.

[piranna]

node-webrtc seems to be active, in the last days is having a lot of movement and in fact the developer of node-rtc has started to collaborate on it... El 15/10/2013 23:30, "Aleksey Mihailiuk" notifications@github.com escribió:

I'm really need it too, but looks like this project is dead.

— Reply to this email directly or view it on GitHubhttps://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26374102 .

[Rantanen]

Issue #1 has been preventing me from really working on this. Trying to keep up with the libwebrtc changes was an exercise in frustration during the summer as there were continuous breaking changes in the interfaces..

I'm still hopeful that the internal APIs of libwebrtc become stable enough at some point and I can find more time from my work to return to this - but regrettably for now I'm too busy with my work to do this.

[fuson]

Is it possible to lock revision of webrtc in build scripts and create binding for this revision?

For now only 2 guys working on webrtc (jingle) binding: https://github.com/modeswitch/node-webrtc (start to datachannel binding) and https://github.com/helloIAmPau/node-rtc (but he start to work on fork of first guy project in https://github.com/helloIAmPau/node-webrtc)

And there is no buildable (for mac) :(

[piranna]

The ideal would be to link against a stable version of libwebrtc and have an unstable branch that link against the bleeding edge, and update the first one after each success of the second one.

2013/10/16 Aleksey Mihailiuk notifications@github.com

Is it possible to lock revision of webrtc in build scripts and create binding for this revision?

For now only 2 guys working on webrtc (jingle) binding: https://github.com/modeswitch/node-webrtc (start to datachannel binding) and https://github.com/helloIAmPau/node-rtc (but he start to work on fork of first guy project in https://github.com/helloIAmPau/node-webrtc)

And there is no buildable (for mac) :(

— Reply to this email directly or view it on GitHubhttps://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26411864 .

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux

[Rantanen]

It is possible - but had I done this in the summer when it became a problem, it would have excluded features such as DataChannel which wasn't implemented in the libwebrtc back then with the current API.

This might be feasible now that the webrtc APIs have stabilized, but it involves first getting the current code to build against the newest libwebrtc.

On Wed, Oct 16, 2013 at 2:58 PM, Aleksey Mihailiuk <notifications@github.com

wrote:

Is it possible to lock revision of webrtc in build scripts and create binding for this revision?

For now only 2 guys working on webrtc (jingle) binding: https://github.com/modeswitch/node-webrtc (start to datachannel binding) and https://github.com/helloIAmPau/node-rtc (but he start to work on fork of first guy project in https://github.com/helloIAmPau/node-webrtc)

And there is no buildable (for mac) :(

— Reply to this email directly or view it on GitHubhttps://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26411864 .

[Rantanen]

"stable version of libwebrtc" - that is assuming there is such a thing. :)

The latest documentation I've found from the webrtc website is dated February 2012: http://www.webrtc.org/reference/native-apis

There is a getting started documentation hosted somewhere there but the only way to find that as far as I know is to google it: http://www.webrtc.org/reference/getting-started

Note how the latest documentation refers to libjingle (Which is part of gtalk/XMPP codebase). The WebRTC bits were originally included in libjingle as the documentation states. The getting started documentation links straight to http://webrtc.googlecode.com though. Originally webrtc.googlecode.com included only the bare minimum WebRTC interfaces with no implementation for them. I guess now they've moved the implementation from libjingle to libwebrtc.

The move away from libjingle sounds good though - I'm hopeful that the new libwebrtc is more useful for third party developers and doesn't contain dependencies to X11, etc. The down side is that since porting from one revision of libjingle to another revision of libjingle wasn't trivial, porting the project from libjingle to libwebrtc is probably quite painful.

But as you said the API should be more stable now that Chrome and Firefox is interoperable.

On Wed, Oct 16, 2013 at 3:31 PM, Jesús Leganés Combarro < notifications@github.com> wrote:

The ideal would be to link against a stable version of libwebrtc and have an unstable branch that link against the bleeding edge, and update the first one after each success of the second one.

2013/10/16 Aleksey Mihailiuk notifications@github.com

Is it possible to lock revision of webrtc in build scripts and create binding for this revision?

For now only 2 guys working on webrtc (jingle) binding: https://github.com/modeswitch/node-webrtc (start to datachannel binding) and https://github.com/helloIAmPau/node-rtc (but he start to work on fork of first guy project in https://github.com/helloIAmPau/node-webrtc)

And there is no buildable (for mac) :(

— Reply to this email directly or view it on GitHub< https://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26411864>

.

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux

— Reply to this email directly or view it on GitHubhttps://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26413577 .

[Rantanen]

Actually I might need to take the "bare minimum WebRTC interfaces" back. Think webrtc.googlecode.com was the actual low level implementation (codecs, network transport, etc) while libjingle contained the public interfaces. In any case the whole of webrtc depended on both projects, libjingle being the main project you needed to build.

On Wed, Oct 16, 2013 at 3:50 PM, Mikko Rantanen jubjub@jubjubnest.netwrote:

"stable version of libwebrtc" - that is assuming there is such a thing. :)

The latest documentation I've found from the webrtc website is dated February 2012: http://www.webrtc.org/reference/native-apis

There is a getting started documentation hosted somewhere there but the only way to find that as far as I know is to google it: http://www.webrtc.org/reference/getting-started

Note how the latest documentation refers to libjingle (Which is part of gtalk/XMPP codebase). The WebRTC bits were originally included in libjingle as the documentation states. The getting started documentation links straight to http://webrtc.googlecode.com though. Originally webrtc.googlecode.com included only the bare minimum WebRTC interfaces with no implementation for them. I guess now they've moved the implementation from libjingle to libwebrtc.

The move away from libjingle sounds good though - I'm hopeful that the new libwebrtc is more useful for third party developers and doesn't contain dependencies to X11, etc. The down side is that since porting from one revision of libjingle to another revision of libjingle wasn't trivial, porting the project from libjingle to libwebrtc is probably quite painful.

But as you said the API should be more stable now that Chrome and Firefox is interoperable.

On Wed, Oct 16, 2013 at 3:31 PM, Jesús Leganés Combarro < notifications@github.com> wrote:

The ideal would be to link against a stable version of libwebrtc and have an unstable branch that link against the bleeding edge, and update the first one after each success of the second one.

2013/10/16 Aleksey Mihailiuk notifications@github.com

Is it possible to lock revision of webrtc in build scripts and create binding for this revision?

For now only 2 guys working on webrtc (jingle) binding: https://github.com/modeswitch/node-webrtc (start to datachannel binding) and https://github.com/helloIAmPau/node-rtc (but he start to work on fork of first guy project in https://github.com/helloIAmPau/node-webrtc)

And there is no buildable (for mac) :(

— Reply to this email directly or view it on GitHub< https://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26411864>

.

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux

— Reply to this email directly or view it on GitHubhttps://github.com/Rantanen/node-peerconnection/issues/3#issuecomment-26413577 .