Repository navigation
MiniClient: negotiate optional media capabilities - #525
Draft
jzhvymetal wants to merge 1 commit into
Draft
jzhvymetal wants to merge 1 commit into
jzhvymetal wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
jzhvymetal
force-pushed
the
sagetv-review/miniclient-capability-protocol
branch
from
September 29, 2026 12:26
a120146 to
175ed34
Compare
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.
Summary
Validation
Review state
Draft protocol proposal: identifiers, versioning, fallback behavior, and cross-client compatibility require OpenSageTV design approval before merge.
This replaces OpenSageTV#10, which was opened against an intermediate fork instead of the canonical SageTV repository. The topic was replayed without patch changes onto the current canonical master.
Maintenance triage (2026-09-29)
Disposition: draft protocol proposal; not requested for merge.
This is not a correction for an existing stock-client failure. It defines optional capabilities used by newer clients while preserving legacy fallback. The focused protocol tests demonstrate internal compatibility, but they do not establish that upstream should adopt the names, command, state ownership, or versioning model.
Do not merge without an upstream design discussion covering identifiers, negotiation/versioning, old-client and old-server behavior, every supported MiniClient implementation, and which capabilities are general SageTV contracts rather than Vibe features.