refactor: clarify resource control boundaries
This commit is contained in:
parent
eb0f69f287
commit
d443b82f1a
5 changed files with 275 additions and 64 deletions
|
|
@ -10,10 +10,13 @@ Within `geth-node`, daemon lifecycle code is separated from feature handlers:
|
|||
`daemon.rs` owns `geth daemon run` startup, local socket binding, shutdown
|
||||
signal handling, Iroh endpoint startup, the Iroh accept loop, and background
|
||||
live-sync task spawning. `local_control.rs` owns async local `ControlRequest`
|
||||
routing and safe trace-field classification before delegating to feature
|
||||
handlers. Runtime registries for pubsub, pipes, and overlays live behind narrow
|
||||
mutex-protected structs in `runtime.rs`. Command-family handler modules and
|
||||
protected peer-control feature dispatch remain separate refactor targets.
|
||||
routing, safe trace-field classification, and named peer/resource/local handler
|
||||
families before delegating to feature implementations. `resource_contracts.rs`
|
||||
records the review boundary for each resource family: resource ID patterns,
|
||||
capabilities, and mutation or host-access points. Runtime registries for
|
||||
pubsub, pipes, and overlays live behind narrow mutex-protected structs in
|
||||
`runtime.rs`. Protected peer-control ALPN dispatch remains a separate refactor
|
||||
target.
|
||||
|
||||
The local metadata store is SQLite product state. `geth-store` tracks a numeric
|
||||
`schema_version` in the `meta` table and applies ordered migrations up to the
|
||||
|
|
|
|||
Loading…
Reference in a new issue