Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #26151

Closed (moved)
Open
Opened May 21, 2018 by David Fifield@dcf

Snowflake rendezvous using Amazon SQS

Nathan Freitas suggests using Amazon Simple Queue Service for exchanging rendezvous messages. "It supports programmatic sending of messages via web service applications as a way to communicate over the Internet."

It looks like messages are relayed through URLs like https://queue.amazonaws.com/ https://sqs.us-east-1.amazonaws.com/ https://sqs.us-east-2.amazonaws.com/ etc.

Here is an example of a SendMessage call: !https://sqs.us-east-2.amazonaws.com/123456789012/MyQueue?Action=SendMessage&MessageBody=Your%20message%20text&Version=2012-11-05&AUTHPARAMS

There's a command-line interface.

I'm not sure how you would send a message back to the client, and have it match up with the message the client sent initially. Maybe a separate queue per client?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26151