Make a "subsystem manager" API to handle module setup/teardown/etc
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Nick Mathewson changed milestone to %Tor: 0.4.0.x-final
changed milestone to %Tor: 0.4.0.x-final
- Author
See branch
subsystems
with PR at https://github.com/torproject/tor/pull/478This code is related to, but not dependent on, the publish/subscribe messaging stuff in #28226 (moved)
Trac:
Status: assigned to needs_review Trac:
Reviewer: N/A to dgoulet- Author
Tor 0.3.6.x has been renamed to 0.4.0.x.
Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final Trac:
Status: needs_review to needs_revisionOh there is another thing about the subsystem
level
. I'm not sure how the values were decided but either way, we would strongly benefit from having them written down in one single place (maybe within the subsystem array?) so when a new one is added, one doesn't have to go through ALL the subsystems to know what level would be good to use.- Author
Okay, I've made the requested changes.
Trac:
Status: needs_revision to needs_review Trac:
Status: needs_review to merge_ready- Author
merged!
Trac:
Status: merge_ready to closed
Resolution: N/A to implemented - Trac closed
closed
- Trac added 12h of time spent
added 12h of time spent
- Trac moved to tpo/core/tor#28330 (closed)
moved to tpo/core/tor#28330 (closed)