feat: add a wire-codec endpoint for network transports#83
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
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.
Adds the wire-codec seam that lets a network transport carry actor operations between nodes while the kernel keeps its concrete, typed events.
System.DeliverWiredecodes a JSON-encoded event into the node's own event typeEand delivers it locally;SpawnWiredecodes a JSON input map and spawns locally. The newWireEndpointinterface (which*Systemsatisfies) is the network counterpart to the in-processEndpoint: where the in-memory transport passes Go values between same-process systems unchanged, a network transport serializes the payload on the sending node and hands the bytes to the owning node'sWireEndpoint, which decodes them intoE. Decoding on the owning node is what keeps the transport type-erased while the kernel stays typed. This is the stdlib-only foundation for the gRPC transport, which lands in its own module so the cluster core carries no network dependency. Coverage: cluster 93 percent. Additive; stdlib-only.