feat(core): delay initial HTTP fallback for first segments#521
Open
feat(core): delay initial HTTP fallback for first segments#521
Conversation
…or first segments
mrlika
force-pushed
the
feat/initial-http-fallback-delay
branch
from
b6e3302 to
cb5bc0e
Compare
DimaDemchenko
approved these changes
Apr 15, 2026
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
2 participants
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.
Description
Introduce a configurable
httpDownloadInitialTimeoutMsparameter that delays falling back to HTTP for the very first segments in the hybrid loader. This delay provides the P2P tracker (and WebRTC dialing) enough time to connect. If a connection is established inside that time window, segments will be loaded via P2P.Changes Included
httpDownloadInitialTimeoutMsconfigurable inStreamConfig. Defaults to0.hybrid-loader.tsdelays HTTP queue processing until the timeout triggers.