Peerjs: Add Support for different signaling servers

[richardanaya]

I really like this project, but the thought of having to run my own backend server for a massively scalable p2p app is a bit daunting. Is there anyway we can use easily us a thirdparty of our choice for the non-webrtc communication? Where would be a good place to start on this?

[piranna]

WebP2P.io, my own signaling library, has support for PubNub backend.

2013/12/2 Richard Anaya [email protected]

I really like this project, but the thought of having to run my own
backend server for a massively scalable p2p app is a bit daunting. Is there
anyway we can use pubnub for the non-webrtc communication? Where would be a
good place to start on this?

—
Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/118
.

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton
de sitios diferentes, simplemente escribe un sistema operativo Unix."
– Linus Tordvals, creador del sistema operativo Linux

[ericz]

@richardanaya

It would make sense in future versions to abstract the signaling so the PeerJS API can be used with any signaling service -- unfortunately this isn't in the near future as there are still lots of issues with the client itself. Once the client is considered stable I think this feature would be a logical next step.

[szimek]

+1. PeerJS is really great, but I'd really like to avoid hosting websocket server myself and just use an external service to handle it for me.

[piranna]

My handshake library WebP2P.io has support for PubNub (in fact I'm doing
the tests on it) and after the major rewrite I have done on it now it's
something really serious :-) I didn't showed it before because I want to
finish to do the tests (I'm really busy the last months...) and also I'm
working on the design on a new protocol focused on data encryption and
anonymity, so this would have been just a private, hardcore devs-only (like
Michelle here at PeerJS or the guys from Peer5) showcase just to discuss
about this new protocol and interoperability between our libraries
projects, but if you are interested you can take a look and give me your
comments :-)

Send from my Samsung Galaxy Note II
El 12/02/2014 20:55, "Szymon Nowak" [email protected] escribió:

+1. PeerJS is really great, but I'd really like to avoid hosting websocket
server myself and use an external service to handle it for me.

Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/118#issuecomment-34909954
.

[szimek]

@piranna Thanks! Do you have any examples? I've just started looking into other signaling options, but what do you think about https://github.com/pubnub/webrtc?

Is there anything specific in PeerJS server that might cause problems replacing it with an external broker that provides presence support like Pusher/PubNub/Firebase?

[piranna]

Currently I don't have examples, just the tests. Anyway I'm focusing on
DataChannels, so maybe it could not be useful to you. I have read a little
bit about the PubNub WebRTC libraries, but I don't find too much advantage
to use them directly, only point it's that their API is more similar to the
one they currently have for their server-based connections.

2014-02-12 21:24 GMT+01:00 Szymon Nowak [email protected]:

@piranna https://github.com/piranna Thanks! Do you have any examples?
I've just started looking into other signaling options, but what do you
think about https://github.com/pubnub/webrtc?

Is there anything specific in PeerJS server that might cause problems
replacing it with an external broker that provides presence support like
Pusher/PubNub/Firebase?

Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/118#issuecomment-34913174
.

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton
de sitios diferentes, simplemente escribe un sistema operativo Unix."

• Linus Tordvals, creador del sistema operativo Linux

[ericz]

Renamed the issue. This is something on the roadmap for the future

[felipecocco]

@ericz, its been a year -- any update on this? Would love to use PeerJS + Firebase for signaling for a project, but a bit stumped on how to proceed.

[szimek]

@felipecocco I've got a modified version of peer.js that uses Firebase in my own project - https://github.com/cowbell/sharedrop/blob/master/app/scripts/vendor/peer.js. I also removed all polyfills that were no longer needed. If you want to use it for data channels, you might want to check if data chunking is still there, because I think I moved it to my app to get notifications about transfer progress. If you have any questions feel free to ask me here or send me an email.

Still it would be awesome to have it built-in, because I bet my version is missing some important fixes that were added to original peerjs since I forked it.

[quantuminformation]

I thought peerJs run their own servers for you as an option?

http://peerjs.com/peerserver

[frankrobert-ls]

Not sure why this was closed @afrokick - Are there any plans on supporting alternative signaling servers other than PeerJS server? As it is today PeerJS server is not enterprise-ready and is a blocker for us to move forward with PeerJS effectively in production.

• Having an internal data structure to keep all ids in-memory prevents us from horizontally scaling or load-balancing the server.
• We don't have granular control over distributing or relinquishing keys.
• We can't monitor the internals of the server nor handle errors effectively.
• We would prefer something that we can offload to a SaaS or possibly different technologies such as a message queue or pub/sub system

It would be great if this was reconsidered.