wiki:org/meetings/2018Rome/Notes/TorModularization

Modularization - Notes

Date: Mar 13th, 2018

Why:

  • Code base is a mess. Monolithic, every part of the code calls every part of the code.

Benefits:

  • Rewrite part of it in Rust.
  • Improved maintainability and testability.
  • Reduce code size so we don't ship everything.

Goal of the session:

What we can do without or/and until we get the funding.

How:

  • Identify which part can be modularize. Have standards on how to create features properly so they are better modularized or easy to modularize later.
  • Use our callgraph tools to identify the parts to extract or need love.

Results:

  • Maybe have our CI do code coverage checks.
  • Make a list of source directory to isolate modules.
  • Try to have a minimal client module for mobile compile time.
  • Dirauth module at compile time.
  • Some sort of design that does publish/subscribe instead of everything calls everything.

List of modules (incomplete):

Level1:

  • Client
  • Relay
    • Hibernation
  • Directory Authority
  • Bridges
  • Hidden Services
    • Client
    • Service
    • HSDir
    • Intro/RP

Level2:

  • Networking
    • Channels/Connections
    • Streams
    • Application Proxy
    • Circuits
  • Statistics
  • Controllers
  • Document Parsing
    • Consdiff/Voting/Descriptors/Consensus
  • CPU Worker
  • Entry Nodes picking logic.
  • PT Management
  • Accounting
  • Handshakes
  • Policy Handling
Last modified 6 months ago Last modified on Mar 23, 2018, 6:45:14 PM