Distinguish original socket binding creation intent #123
No reviewers
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/lib-ipc!123
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/explicit-socket-binding-creation"
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?
Carry socket binding creation as an explicit original intent. Preserve complete correlation and creation policy without treating an existing binding or descriptive address as permission to create another object.
Depends on #122.
WIP: Distinguish original socket binding creation intentto Distinguish original socket binding creation intentReconciled at
86d11e71b8e835aef0e8f71311037cd8fea458f7onfeature/explicit-socket-binding-creation-merge-ready-86d11e71. Socket creation remains a separate metadata-only intent. The reply kind must match that original intent; an existing binding or reported address does not authorize creating another object.The original work branch is preserved. Matching provider/runtime adoption and guest acceptance remain separate. Please review this exact prepared commit; earlier approval does not cover the rewritten history.