Opened 18 months ago

Last modified 8 weeks ago

#29213 new enhancement

Minimize the boundary between src/core and src/{feature,app}

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 043-deferred, 044-deferred
Cc: Actual Points:
Parent ID: Points: 15
Reviewer: Sponsor:

Description

The API boundary between src/core and higher level layers is more or less nonexistent. That's not surprising, since we created this distinction by moving files and functions around.

We can actually do much better here. Possibile strategies include:

  • Removing up-calls from src/core to src/{feature,app}
  • Designing an API for the code, and adjusting external modules to use that.
  • Moving more pieces outside of sec/core as appropriate

Child Tickets

Change History (7)

comment:1 Changed 16 months ago by nickm

Milestone: Tor: 0.4.2.x-final

Tentatively placing some roadmapped tasks for s31 into 0.4.2.

comment:2 Changed 11 months ago by nickm

Type: defectenhancement

Mark a number of current 0.4.2.x "defects" as "enhancements."

comment:3 Changed 11 months ago by nickm

Milestone: Tor: 0.4.2.x-finalTor: 0.4.3.x-final

Defer several enhancements from "new" to 0.4.3.

comment:4 Changed 6 months ago by nickm

Keywords: 043-deferred added

All 0.4.3.x tickets without 043-must, 043-should, or 043-can are about to be deferred.

comment:5 Changed 6 months ago by nickm

Milestone: Tor: 0.4.3.x-finalTor: 0.4.4.x-final

comment:6 Changed 6 months ago by gaba

Sponsor: Sponsor31-can

No more sponsor 31. All this tickets remained open after sponsor 31 ended.

comment:7 Changed 8 weeks ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Note: See TracTickets for help on using tickets.