PeerJS — True peer-to-peer data in the browser(peerjs.com)

110 pointsby andrewnezvor 13 Jahren24 comments

PeerJS — True peer-to-peer data in the browser

http://peerjs.com/

6 comments

> Note that no peer-to-peer data goes through the server; The server acts only to broker connections.

Q1. Does this support connecting to a peer behind a NAT device?

Q2. Does this support connecting two peers each behind its own NAT?

Because a vast majority of real world cases will fall into either of these two categories.

churreirovor 13 Jahren

It is NAT reversal, even there are still many issues to be solved with the ICE. WebRTC team is working fast in this aspect...

BTW, consider that they are shipping first final version in march so NAT reversal is important. YEY!

vr000mvor 13 Jahren

It uses SDP to exchange ICE candidates. At the moment the SDP tries to multiplex video/audio and SCTP (data channel).

latitudevor 13 Jahren

Does WebRTC have any sort of extension mechanism whereby I can drop in my own version of NAT traversal logic?

Speaking from past experience, STUN and ICE are OK, but they got the whole process fundamentally wrong. They let the clients drive the traversal process. This is substantially inferior to letting a dedicated mediating server do that instead. I did that with one of my past projects and it helped with connecting peers in a large number of obscure scenarios.

vr000mvor 13 Jahren

you can add one or more TURN server(s) into the mix, but apart from that there is no other way using just Javascript.

churreirovor 13 Jahren

You should hack the Chromium webkit for this.

ericzvor 13 Jahren

ICE/STUN (which is used by WebRTC and thus PeerJS) support NAT traversal in all cases but a pair of symmetric NATs, which means some single digit percentage of connections will not work. For those cases, WebRTC/PeerJS support using a TURN server which proxies the data, not ideal but it allows the library to work.

vr000mvor 13 Jahren

AFAIK, you will be/are able to add TURN server addresses to the mix. It is possible that chrome uses google's TURN servers by default.

dalorevor 13 Jahren

Handles NAT traversals

huhtenbergvor 13 Jahren

Any details?

churreirovor 13 Jahren

http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtciceserve...

Specifications here

[deleted]vor 13 Jahren

Hupovor 13 Jahren

Looks like a nice little library, and very relevant to my interests. My personal "dream scenario" is to have true multisource P2P video streaming in the browser with no extensions required - with WebRTC, this seems quite feasible as implementations mature.

jonpaulvor 13 Jahren

Check out Holla.js for that: https://github.com/wearefractal/holla

muyuuvor 13 Jahren

Any video streaming demo?

mgurlitzvor 13 Jahren

See the demo at http://holla.jit.su/

samwillisvor 13 Jahren

This looks like a really nice abstraction of the API. Will have to have a play with it over the weekend and see what ideas I come up with....

You can play with their chat demo here: http://cdn.peerjs.com/demo/chat.html

(Google Chrome 26.0.1403.0 or above is required)

[deleted]vor 13 Jahren

venomsnakevor 13 Jahren

Is a torrent client for iOS finally possible with that? One that runs in the browser and will piss off apple.

nwhvor 13 Jahren

Potentially, but their Safari browsers don't support webRTC yet. There's also nothing you could do with the files once you had them, other than images.

I'd personally like to see them implement proper SVG support before they do too.

jonkneevor 13 Jahren

Kind of hard when you can't store to the filesystem.

venomsnakevor 13 Jahren

Direct torrents no, but you can rename the pieces *.fll and download them and send them to registered app for that extension that combines them ... you will have problem with seeding though, but that is also something that can be solved with a little tweaking of the protocol. I think the hacker community has shown that they can scare you with their inventiveness when they work in (stupidly and unnecessarily in that case) constrained environment.

silverlightvor 13 Jahren

Any reason not to offer support for the video side of things? A lot of the issues in terms of client IDs and whatnot are the same. It would be nice to have a single library that can establish a connection and then send either video ir data or both...

churreirovor 13 Jahren

Is it totally possible to do both with the same library.Problem is: You need that?

I mean, video rendering kills the performance of your browser I guess is better just to show the possibility of data transferring and then you build it by using the desired specs. Many ongoing video demos are avaliable too :)

http://webp2p.org/

Those guys are also in the same ship with the browser P2P using WebRTC.

jonpaulvor 13 Jahren

Check out Holla.js for Video/Audio: https://github.com/wearefractal/holla

ericzvor 13 Jahren

It's in the works!

[deleted]vor 13 Jahren