Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #28848
Closed
Open
Issue created Dec 14, 2018 by Alexander Færøy@ahf🍍

Document Snowflake broker implementation

We should document how the current Snowflake implementation distributes Snowflake proxies to clients that is in need of them.

Once we have specified how the current implementation works, we should figure out if there are things we would like to change before we can start shipping Snowflake in an alpha state to users.

  1. Look at broker code in the Snowflake repository.
  2. Document current behavior with long-polling clients waiting to get handed a proxy.
  3. Let's discuss if this design have any weaknesses we would like to address.

One weakness here could be that currently the broker nor client DOES NOT pass information about which bridge/relay to connect to, but this bridge/relay host is hardcoded in both the Go and JS proxy code.

Assignee
Assign to
Time tracking