[FEATURE] Use owned invocations for renderer calls #46
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/ttyd#46
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
Keep the terminal loop responsive while framebuffer requests await their results. Align the renderer client with the owned request protocol already served by Fbcond.
Proposed behavior and scope
Retain the existing Submit, Poll, Pending and Reply behavior. Submit each renderer operation once, retain its actual pending owner, and collect its eventual result into a fresh call-local buffer. Preserve rendering order, backpressure, response codes and terminal activity while a request is pending.
Use the existing LibIPC owned invocation adapters and Fbcond serving interface. This change covers the renderer client and its matching service contract; it does not establish generic legacy CALL compatibility or release-image acceptance.
Authority, security and reliability
Use only the originally supplied renderer endpoint and its existing rights. These requests carry no capabilities and need no additional GRANT authority. Retain pending, serving and draining duties through cancellation, source withdrawal and result release. Packet fields and numeric selectors cannot create another request owner. Submission failure must leave no partial operation or surplus authority.
Acceptance criteria
Alternatives and tradeoffs
Blocking the terminal loop would lose responsiveness. Retaining a native owned result until explicit collection reuses the existing protocol and keeps buffer access within individual calls. Compatibility outside this renderer path remains separately tracked.
Tracking and rollout
Build on Ttyd #45, Fbcond #4 and LibIPC #184. Implement and review the complete caller/service slice before selecting it for the native image. Remove the superseded renderer polling path after preserving its behavior and failure coverage.
The framebuffer client implementation is in #47. It preserves pending work and exact replies through owned submission, collection and release, with serial routes kept separate. The checked items cover client implementation and host controls; native lifecycle, matching-image and multicore demonstrations remain open.