Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7508

Closed (moved)
(moved)
Open
Created Nov 18, 2012 by Damian Johnson@atagar

Stream purposes are undocumented

In general the control spec is pretty good about saying what event attributes indicate. One exception are stream purposes which are completely undocumented.

https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt#l1411

atagar@morrigan:~/Desktop/tor/torspec$ grep -R "UPLOAD_DESC" ./*
./control-spec.txt:      Purpose = "DIR_FETCH" / "UPLOAD_DESC" / "DNS_REQUEST" /

atagar@morrigan:~/Desktop/tor/torspec$ grep -R "DNS_REQUEST" ./*
./control-spec.txt:      Purpose = "DIR_FETCH" / "UPLOAD_DESC" / "DNS_REQUEST" /

... etc...

See the StreamStatus above for an example of a nice mapping between attributes and a description.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking