Live data from Hacker News

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

peerjs.com

11–20 of 28 posts

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

#11

> 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.

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!

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

#13

> 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.

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

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

#15
post #13

> 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.

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

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.

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

#16
post #13

Earlier quoted context omitted.

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

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 connectin…

You should hack the Chromium webkit for this.

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

#17
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.

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

#20

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...

Check out Holla.js for Video/Audio: https://github.com/wearefractal/holla
Post reply on HN