Re:WebRTC DataChannels just hit Chrome stable
by erbbysam on Wednesday March 27, 2013 @07:45AM
(#5448797)
There is a hack to get around this (in Chrome) by increasing the SDP channels transfer rate (I think), still doesn't solve the MTU/reliable issue though. I originally found it via ShareFest - https://github.com/Peer5/ShareFest/issues/10 & have it integrated (in library form) here - https://github.com/erbbysam/webRTC-data.io
I haven't tested this yet on Chrome Stable though.
Re:WebRTC DataChannels just hit Chrome stable
by dbaupp on Wednesday March 27, 2013 @03:48AM
(#5448289)
And it's been in Firefox for a while too. (Nightly only, maybe?)
Re:WebRTC DataChannels just hit Chrome stable
by dveditz on Thursday March 28, 2013 @03:56PM
(#5457243)
It is currently enabled in nightly (Fx22) and Aurora (fx21). No promises it won't get turned off in Fx21 before ship but that appears to be the current target release.
Re:WebRTC DataChannels just hit Chrome stable
by ninjay on Wednesday March 27, 2013 @04:46AM
(#5448400)
I always thought it would be cool to do distributed cache in browsers with this technology. It would be like an organic CDN, automatically making the internet faster.
Re:WebRTC DataChannels just hit Chrome stable
by jychang on Wednesday March 27, 2013 @06:00AM
(#5448557)
Might want to check this out: https://github.com/PeerKit/peercdn
It's written with PeerJS, by one of the other creators of PeerJS, same as OP.
Re:WebRTC DataChannels just hit Chrome stable
by DanielRapp on Wednesday March 27, 2013 @06:36AM
(#5448633)
Looks neat, do you know if they're planning on open sourcing the server implementation as well?
Re:WebRTC DataChannels just hit Chrome stable
by DanielRapp on Wednesday March 27, 2013 @05:18AM
(#5448472)
That's precisely what I'm building https://github.com/DanielRapp/peerbalanced ;)
Re:WebRTC DataChannels just hit Chrome stable
by JulianMorrison on Wednesday March 27, 2013 @05:41AM
(#5448521)
Cache poisoning with spam in 3, 2, 1...
Also note that currently DataChannels do not support reliable transfer and have a small MTU, so sending enormous files does not yet work. With PeerJS you can send smaller files, but larger ones will take an unreasonable amount of time.