[FEATURE] Publish exact native outputs through retained provider transactions #12
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/ramfsd#12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Native build tools need to replace an existing output atomically while preserving it until the replacement is complete. The fixed-entry rename API intentionally refuses an occupied destination.
Proposed behavior and scope
Add a provider transaction behind Vfsd's exact-output publication endpoint: Begin, confirmed-prefix Write, Sync, CloseWriter, Commit, Abort and Status. Retain the original parent, destination binding or absence, and adjacent temporary until the transaction settles. Keep existing fixed-entry operations unchanged.
Authority, security and reliability
Only the original retained provider handle admits operations. Native callers cannot choose another parent, mode or object key. CloseWriter closes writing while retaining publication pins. Commit replaces only the original destination; a moved or rebound entry conflicts. Abort removes only the unpublished original temporary. Lost observations never authorize replay, rebinding or ordinary reuse.
Reserve actual in-memory capacity before atomic replacement. All write/truncate aliases advance shared content revisions so an equal-size rewrite cannot invalidate Sync silently.
Acceptance criteria
Alternatives and tradeoffs
Do not widen ordinary fixed-entry rename into a path-selected replacement API. A dedicated retained transaction keeps temporary cleanup and atomic publication under the same original owner.
Tracking and rollout
See Boot-tool's native backend, broker attenuation and phase 6 tracking. Coordinate protocol producers and consumers before enabling native publication.
erikinkinen referenced this issue2026-10-30 18:06:26 +01:00