WebRTC P2P Data Stream

[jinroh]

http://dev.w3.org/2011/webrtc/editor/webrtc.html
http://dev.w3.org/2011/webrtc/editor/webrtc.html#peer-to-peer-connections
http://arstechnica.com/business/news/2012/01/hands-on-building-an-html5-photo-booth-with-chromes-new-webcam-api.ars
http://blog.chromium.org/2012/01/real-time-communications-in-chrome.html
http://www.webrtc.org/
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15206

[alexstrat]

http://blog.chromium.org/2012/04/chromes-webrtc-roadmap.html

[piranna]

I've been developing during the last weeks a DataChannel polyfill from the specs using a WebSockects based proxy server. It's far from perfect, but it's API compatible and since it's main purposse is to allow to experiment with the API until we have some native implementation, it works :-D You can find it at https://github.com/piranna/DataChannel-polyfill, and on the test folder you can find a simple test showing how it works (it's based on webrtc.io demo code, only that the video code is removed and it's adapted so it's easy to integrate with my ShareIt! project (https://github.com/piranna/ShareIt)).

[alexstrat]

Thanks for this reminder ! I was actually surveying your project with a distant (I am a bit busy these times..) but interested eye. We are currently crossing a massive "refactor modularise and documente all" step, but we are looking forward to try webrtc and I'll think we'll try with your polyfill while waiting for the actual implementation.

We'll let you know !

Le 15 sept. 2012 à 02:29, Jesús Leganés Combarro [email protected] a écrit :

I've been developing during the last weeks a DataChannel polyfill from the specs using a WebSockects based proxy server. It's far from perfect, but it's API compatible and since it's main purposse is to allow to experiment with the API until we have some native implementation, it works :-D You can find it at https://github.com/piranna/DataChannel-polyfill, and on the test folder you can find a simple test showing how it works (it's based on webrtc.io demo code, only that the video code is removed and it's adapted so it's easy to integrate with my ShareIt! project).

—
Reply to this email directly or view it on GitHub.

[piranna]

Thank you for your comments! :-D I have just finished some minutes ago to remove the '_datachannel' array from the polyfill to the client code so it's now fully standard and fixed some bugs, and also added a minimal test that also works as example code for the API :-) Currently it's working on Chromium >= 21 since it has the PeerConnection object but don't the DataChannel API (that's the reason i build it), on Firefox there are more problems since it's only implemented the getUserMedia API and all the WebRTC work is being done at once on a different branch (v18a 'alder') and it's more difficult to test it, i'll give it another try now that i have the test working :-)

[piranna]

It seems Chrome v24 Dev and Firefox 18 Aurora support DataChannels natively (although personally I didn't be able to make them work...). Is there any "private" improvement here? Are you still busy? Can I help you in anything? :-)

[mjp0]

Any updates on this?

[dysbulic]

I created a $50 bounty for someone fixing this.

[alexstrat]

I think you should have a look to https://github.com/feross/webtorrent

[jure]

👍 If not KadOH, who then? WebRTC could bring a lot of life to the project. It's the first time that KadOH can actually be really P2P without XMPP relays in the network, etc.

[gustavorps]

Bountysource decided to update their Terms of Service:

2.13 Bounty Time-Out.
If no Solution is accepted within two years after a Bounty is posted, then the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource. For Bounties posted before June 30, 2018, the Backer may redeploy their Bounty to a new Issue by contacting [email protected] before July 1, 2020. If the Backer does not redeploy their Bounty by the deadline, the Bounty will be withdrawn and the amount posted for the Bounty will be retained by Bountysource.

https://www.bountysource.com/issues/974464-webrtc-p2p-data-stream