feat(catchup): wire M3U archive intent through catalog resolution - #303
Closed
MrFr3di wants to merge 9 commits into
Closed
feat(catchup): wire M3U archive intent through catalog resolution#303MrFr3di wants to merge 9 commits into
MrFr3di wants to merge 9 commits into
Conversation
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.
Superseded by merged #304 /
main@a84307a1307efe3377daaa10c711bda12970bdb2.This alternative explored extending
PlaybackReferenceResolverwithPlaybackIntent, catch-up metadata andMaterializedDirect. The accepted #304 keeps a narrower separation instead:PlaybackReferenceResolverremains responsible for persisted provider-reference -> ephemeral transport resolution;PlaybackArchiveResolverowns explicit archive-intent/timeline materialization;RoomPlaybackCatalog.resolveIntent()feeds the materialized locator back into the existingPlaybackAccessCoordinator, so credential/exact-origin policy remains authoritative.That avoids widening the existing reference-resolution contract with archive semantics and avoids chaining M3U catch-up as a fallback wrapper around the Xtream reference resolver. #304 passed exact-head Hosted validation #2050, Hosted CI contract #319, DB API26/API36 #641, App TV lint #254 and focused API36 #424. Do not merge this alternate branch.