[FEATURE] Use owned invocations for renderer calls #46

Open
opened 2026-11-06 18:44:50 +01:00 by erikinkinen · 1 comment
Owner

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

  • Submit once, continue terminal work while pending, and collect the exact eventual result.
  • Preserve identical request/reply bytes, malformed-response refusal, backpressure and effect ordering.
  • Keep unrelated blocking calls and receive state independent from renderer completion.
  • Cover source withdrawal, receiver replacement, caller exit, allocation failure and acknowledged cleanup without duplicate effects.
  • Verify the actual Ttyd/Fbcond request and result contracts and document the interface migration.
  • Demonstrate the matching renderer path in the composed native image, including multicore execution.

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.

## 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 - [x] Submit once, continue terminal work while pending, and collect the exact eventual result. - [x] Preserve identical request/reply bytes, malformed-response refusal, backpressure and effect ordering. - [ ] Keep unrelated blocking calls and receive state independent from renderer completion. - [ ] Cover source withdrawal, receiver replacement, caller exit, allocation failure and acknowledged cleanup without duplicate effects. - [ ] Verify the actual Ttyd/Fbcond request and result contracts and document the interface migration. - [ ] Demonstrate the matching renderer path in the composed native image, including multicore execution. ## 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](https://git.erikinkinen.fi/erix/ttyd/pulls/45), [Fbcond #4](https://git.erikinkinen.fi/erix/fbcond/pulls/4) and [LibIPC #184](https://git.erikinkinen.fi/erix/lib-ipc/pulls/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.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 18:44:50 +01:00
Author
Owner

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.

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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/ttyd#46
No description provided.