This is not actually Peer to Peer #8

tommedema opened this Issue Apr 28, 2012 · 4 comments


None yet
2 participants

You've been stating that this is an example of peer to peer in the browser. Most importantly, peer to peer implies that there is no need for a central server.

Conversely, this project is as dependent on a central server as dependency can go. So I've been wondering, why are you calling this peer to peer? Because data is not permanently stored on the server? That's completely irrelevant.

The way I see it, you only have limited options for peer to peer with node.js:

  1. You'd have to write a client-side bridge for the actual P2P communication (as this cannot run in the browser)
  2. You'd have to use Adobe Flash, with all its downfalls (RTMFP)

The first case has never been accomplished in node.js before, as far as I know. You'd need to have a great deal of knowledge about firewalls, networking, etc. And even so, many corporate firewalls won't allow any P2P traffic (RTMFP also suffers from this, a great many people cannot use it without going in to their router's settings).

The second case is almost certainly a no-go, due to numerous issues


Miserlou commented May 7, 2012

This is a placeholder for when WebRTC-data becomes stable. Keep your eyes peeled. :)


Miserlou commented May 7, 2012

Closing as a duplicate: #4

@Miserlou Miserlou closed this May 7, 2012

Nice, that'll be interesting. Thanks for the reply.


Miserlou commented May 7, 2012

If you want to discuss what we're doing with that, please join the webp2p mailing list by emailing !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment