Must stay up all night and develop first DataChannel based P2P BitTorrent style file sharing implementation tonight..
Make haste! People on Canary had a head start :P. 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.
WebRTC DataChannels just hit Chrome stable
11–20 of 26 posts
Re: WebRTC DataChannels just hit Chrome stable
#12Someone should build a meshnet!
Re: WebRTC DataChannels just hit Chrome stable
#13The docs say "Note that the server is only for brokering connections and does not proxy data between peers." So what browser API does the PeerJS use to exchange data with something other than a server, particularly another browser? Is this it? https://tools.ietf.org/html/draft-jesup-rtcweb-data-protocol...
Re: WebRTC DataChannels just hit Chrome stable
#14Must stay up all night and develop first DataChannel based P2P BitTorrent style file sharing implementation tonight..
Re: WebRTC DataChannels just hit Chrome stable
#15Earlier quoted context omitted.
Make haste! People on Canary had a head start :P. 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.
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
#16Earlier quoted context omitted.
Make haste! People on Canary had a head start :P. 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.
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
#17Earlier quoted context omitted.
Make haste! People on Canary had a head start :P. 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.
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.
It's written with PeerJS, by one of the other creators of PeerJS, same as OP.
Re: WebRTC DataChannels just hit Chrome stable
#18Earlier quoted context omitted.
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.
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
#19Must stay up all night and develop first DataChannel based P2P BitTorrent style file sharing implementation tonight..
It's the only one I've seen that abides to the bittorrent spec (where possible). BEP 9 and 10 support incoming.
(Demo's broken, need to push a fix :()
Re: WebRTC DataChannels just hit Chrome stable
#20Must stay up all night and develop first DataChannel based P2P BitTorrent style file sharing implementation tonight..
Make haste! People on Canary had a head start :P. 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.