feat: add browser MessagePort transport#1334
Draft
rvolosatovs wants to merge 1 commit into
Draft
Conversation
Add the `wrpc-message-channel` crate, a wRPC transport over a browser `MessagePort` (one half of a `MessageChannel`, or a port transferred from a worker/window). A `MessagePort` is a single established bidirectional message stream, so it maps onto one wRPC connection that the framed transport multiplexes into an invocation's sub-streams. `connect` bridges the event-based `MessagePort` API onto the `AsyncRead`/`AsyncWrite` byte-stream halves the framed transport expects. Since `MessagePort` is `!Send` while `Invoke`/`Serve` require `Send`, the port is moved into a `spawn_local` task and reached only through `Send` channels; the returned halves are `Send` and satisfy the bounds. Each direction is framed as discrete messages: a `Uint8Array` carries a chunk of bytes and a `null` message is the end-of-stream sentinel. `Client` is a one-shot `Invoke` and `Server` reuses the framed server. The crate is gated to `cfg(target_family = "wasm")` (empty elsewhere) and wired into the `wrpc` facade behind a non-default `message-channel` feature, re-exported as `transport::message_channel`. Assisted-by: claude:claude-opus-4-8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the
wrpc-message-channelcrate, a wRPC transport over a browserMessagePort(one half of aMessageChannel, or a port transferred from a worker/window). AMessagePortis a single established bidirectional message stream, so it maps onto one wRPC connection that the framed transport multiplexes into an invocation's sub-streams.connectbridges the event-basedMessagePortAPI onto theAsyncRead/AsyncWritebyte-stream halves the framed transport expects. SinceMessagePortis!SendwhileInvoke/ServerequireSend, the port is moved into aspawn_localtask and reached only throughSendchannels; the returned halves areSendand satisfy the bounds. Each direction is framed as discrete messages: aUint8Arraycarries a chunk of bytes and anullmessage is the end-of-stream sentinel.Clientis a one-shotInvokeandServerreuses the framed server.The crate is gated to
cfg(target_family = "wasm")(empty elsewhere) and wired into thewrpcfacade behind a non-defaultmessage-channelfeature, re-exported astransport::message_channel.Assisted-by: claude:claude-opus-4-8