Oh, and if you want to get a picture of what chrome (assuming you are using chrome) is doing in the background use this url: chrome://webrtc-internals/
Sweet layout - love it. Also while there was no hope of any client being able to decode that amount of video at one time I think it does show that the overheads of a RTCPeerConnection (without media) aren't extreme. My…
I think there has been some progress made on implementing BitTorrent like clients using WebRTC data channels: https://github.com/feross/webtorrent I haven't done that much investigation myself yet, but I definitely…
I agree with that comment, which was one of the reasons rtc.io was created in the first place. A lot of the other libraries hide away the core browser objects through higher-level JS objects, whereas the core rtc.io…
It does work best with the signaller from the rtc.io suite: https://github.com/rtc-io/rtc-signaller That said, it wouldn't take much to write an signalling client that followed the basics of the messaging format if you…
The client portions are definitely in the library, and as you point out the node-webrtc library is looking really promising for interop with server processes. If you need any help with the POC that you are currently…
Thanks to a project that has been previously pointed out (node WebRTC bindings - https://github.com/js-platform/node-webrtc) interop between a browser and node applications isn't too far away. There is this issue which…
Oh, and if you want to get a picture of what chrome (assuming you are using chrome) is doing in the background use this url: chrome://webrtc-internals/
Sweet layout - love it. Also while there was no hope of any client being able to decode that amount of video at one time I think it does show that the overheads of a RTCPeerConnection (without media) aren't extreme. My…
I think there has been some progress made on implementing BitTorrent like clients using WebRTC data channels: https://github.com/feross/webtorrent I haven't done that much investigation myself yet, but I definitely…
I agree with that comment, which was one of the reasons rtc.io was created in the first place. A lot of the other libraries hide away the core browser objects through higher-level JS objects, whereas the core rtc.io…
It does work best with the signaller from the rtc.io suite: https://github.com/rtc-io/rtc-signaller That said, it wouldn't take much to write an signalling client that followed the basics of the messaging format if you…
The client portions are definitely in the library, and as you point out the node-webrtc library is looking really promising for interop with server processes. If you need any help with the POC that you are currently…
Thanks to a project that has been previously pointed out (node WebRTC bindings - https://github.com/js-platform/node-webrtc) interop between a browser and node applications isn't too far away. There is this issue which…