Add distributed store support.

[tsujio]

In this patch PeerServers compose a cluster and they forward client's message to the other PeerServer if the dst of the message is not found in the local _clients property.

PeerServers find which server to forward messages by memcached shared by the cluster.

[jure]

Wow! Are you kidding me?! This is fantastic! Great work, @tsujio!

Given that one of the big limitations for scalability for self-hosted PeerJS is the number of WebSocket connections each individual server can handle, this is a great step towards removing that obstacle.

Not really sure if this belongs directly to PeerJS server, but this is an awesome use-case for extensions.

[michelle]

Sorry for the delay! Looking at this now :).

[michelle]

Awesome work! I'm ==@jure that this likely doesn't belong in peerjs-server master, but would love to consider ways to make the server more extensible for things like this (let me know if you have any thoughts!).

I'm going to play around with this implementation a bit to see how it could be rewritten as an extension (and what changes to the PeerJS server are necessary).

Thanks again!

[ummjackson]

Unfortunately this still centralizes around shared memcached instances... would be great to have some sort of mesh-database system going between PeerServers without the need for sharing memcached.

[jure]

This is more about scaling than it is about decentralization. For a maximally decentralized network (given the signaling constraints), take a look https://github.com/boplish/core or more specifically boplish/core#4.

[Iragne]

very interesting If we can merge this request in the master ??