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.

Sign up for GitHub

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

Jump to bottom

Hypercore network reliability and fallback #4

Open
urbien opened this issue Sep 22, 2020 · 0 comments
Open

Hypercore network reliability and fallback #4

urbien opened this issue Sep 22, 2020 · 0 comments

Comments

@urbien
Copy link
Member

urbien commented Sep 22, 2020 •
edited
Loading

Problem

the default is to use TCP in Hypercore. TCP may be blocked by the firewall and is not available in the browser.

Fallback

  1. if in Browser, skip to 3

  2. start with uTP, if fails, next
    Coudl we use UDP port 443, which is used by QUIC?

  3. use TCP. If fails, next

  4. use WebRTC. What extra info do we need for this?

  5. Relay. if P2P connection fails, establish a proxy connection via Relay.
    Use Personal Cloud for that to avoid privacy loss.

It is probably better to do them in parallel, e.g. Chrome currently races TCP and QUIC connections instead of waiting for a QUIC timeout.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@urbien