Skip to content

Conversation

@rekmarks
Copy link
Member

Progresses: #369

Continues the work of #369 by replacing the "vat worker" command / reply types with the pattern introduced in #474. This primarily affects the extension, since only its VatWorkerManager (so renamed from VatWorkerService) logically crosses process boundaries. Its Node.js counterpart is just a class that lives next to the kernel, and is only affected by some renamed types.

…ttern

- Standardize naming of VatWorkClient / Service types and classes across
  monorepo
- Forego use of RpcService in extension due to exceptional nature of its
  VatWorkerService (passing message ports around)
@rekmarks rekmarks requested a review from a team as a code owner April 11, 2025 00:04
@rekmarks rekmarks mentioned this pull request Apr 11, 2025
5 tasks
@rekmarks rekmarks enabled auto-merge (squash) April 11, 2025 00:11
Copy link
Contributor

@sirtimid sirtimid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rekmarks rekmarks merged commit fcca236 into main Apr 11, 2025
21 checks passed
@rekmarks rekmarks deleted the rekm/rpc-vat-worker-service branch April 11, 2025 09:03
rekmarks added a commit that referenced this pull request Apr 22, 2025
…#487)

Closes: #369 

Replaces all kernel and vat "message" types with the new `RpcClient` /
`RpcService` pattern. For related work and the justification for this,
see:
- #369
- #474 
- #481 

Note that, in the course of implementing this refactor, it was
discovered that we are never returning _any_ responses to syscalls
originating from vat supervisors. This PR maintains a provisional
solution using the new pattern, and #488 tracks the work to actually fix
this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants