Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify that signaling server is online before using it #3

Open
jrhea opened this issue May 14, 2018 · 0 comments
Open

Verify that signaling server is online before using it #3

jrhea opened this issue May 14, 2018 · 0 comments
Assignees

Comments

@jrhea
Copy link
Member

jrhea commented May 14, 2018

What is the best way to handle offline signaling servers?

Does Infura have one we can count on? If not, we eventually need to host our own.

In the meantime, here are the ones that I know protocol labs make available:

/dns4/ws-star-signal-2.servep2p.com/tcp/443/wss/p2p-websocket-star
/dns4/ws-star-signal-1.servep2p.com/tcp/443/wss/p2p-websocket-star
/dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star

Tried adding all of them to the Swarm array in hopes that it would fail over to the available one, but it didn't seem to work like that (this needs to be verified though).

Could specifically check (in code) to see which one is online before using it.

Note: In chrome I can navigate to: ws-star-signal-2.servep2p.com to see if it is up and running. This needs to be done in code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants