docs: add the shared-core boundary recommendation and deck - #568
Open
gavrie wants to merge 1 commit into
Open
Conversation
Where the line sits between band-sdk-core and each language's SDK: ship core-protocol across the FFI boundary and let every consumer own its own I/O. - docs/rust-core-recommendations.md — the full recommendation, with a glossary for readers without a Rust background, twelve sections, and an appendix on what a Go SDK would change. - docs/rust-core-recommendations-deck.html — a self-contained presentation of the same argument, 16 pages, no external assets. Authored by Gavrie Philipson, based on input from and discussions with Amit Gazal, Nir Singher and Alexander Zaikman.
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.
The recommendation: ship
core-protocolacross the FFI boundary and let every consumer own its own I/O. The shared core is the sans-io protocol logic — session state machine, reconnect planner, disconnect taxonomy, frame codec, rejoin policy. Each SDK drives it with its own transport, on its own runtime, using its own sockets.Landing here rather than in the Rust core repo, which has since been archived.
Files
docs/rust-core-recommendations.mddocs/rust-core-recommendations-deck.htmlAuthored by Gavrie Philipson, based on input from and discussions with Amit Gazal, Nir Singher and Alexander Zaikman.