Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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
  • #14683

Closed (moved)
(moved)
Open
Created Feb 02, 2015 by Nick Mathewson@nickm👉

Document medium-scale design of key Tor abstractions

In between the specs and the doxygen documentation, there isn't much to explain why our subsystems work that way, how they fit together, and so on.

Some areas we should really elaborate are:

  • circuits
  • cmux
  • circuitpathbias
  • entrynodes
  • channels
  • the main event loop/connection abstraction

We should probably try to make it a practice to always document new things, and to fill in documentation for older things as we can. Whatever has changed most recently is probably going to be freshest on our minds, so let's start there.

I'm putting this in 0.2.??? as non-blocker, but we should try to get more stuff documented whenever the opportunity exists.

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