Repository navigation
Proposal (draft): named connections - #185
Merged
Merged
Conversation
added 2 commits
November 15, 2026 11:42
Draft. Lays out one connection per package (with a package per application) against named sets declared in the manifest, in the IDL, or by a world-like declaration, with prior art. Every choice is an open question.
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.
Draft proposal, not for merge: nothing in it is decided. Every choice is an open question for the user.
A package gets exactly one connection today (one
Services,ClientServices,accept,serve,connectandConnection<T>). This proposal sets out letting a package declare several named sets of protocols, each generating entry points of its own, against keeping one connection per package and one package per application. It develops the declared set that Connections decision 2 (2026-10-20) left unbuilt.Pages, under
docs/docs/proposals/named-connections/:index.md: the question, where things stand (checked against the docs, generation and the runtime), a comparison table, 15 numbered open questions, and what it touches.options.md: Option 0 (status quo, Proposal C's model), 1 (sets in the manifest, inconfig.idporcomline.toml), 2 (aconnectionblock or an annotation), 3 (a world-like declaration that can name dependency protocols, tying into Proposal A); what each generates and checks, versioning, tools, migration.prior-art.md: protoc and Buf, gRPC and tonic, Thrift, Cap'n Proto, Smithy, WIT, FIDL and Mojo, each claim with its source.Also lists it in
proposals/index.md(Connections, with the other drafts) and in themkdocs.ymlnav.The strict
buildjob is the check; mkdocs was not built locally.