From: Steven Liu <lingjiujianke-at-gmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC PATCH] avformat: remove HLS protocol Date: Thu, 10 Jul 2025 08:43:12 +0800 Message-ID: <CADxeRw=QrNitNFWE1go5SXAFvPhQbMYNG9iwvqxn4GWYYSSZ1Q@mail.gmail.com> (raw) In-Reply-To: <CADxeRwmU2A3OS8jTF8MCxLkA311L_t+tA5iYg8NaDKoWx6ekWw@mail.gmail.com> Steven Liu <lingjiujianke@gmail.com> 于2025年7月10日周四 04:42写道: > > > > Timo Rothenpieler <timo@rothenpieler.org>于2025年7月9日 周三23:33写道: >> >> On 7/9/2025 3:28 PM, Marvin Scholz wrote: >> > >> > >> > On 9 Jul 2025, at 11:18, Steven Liu wrote: >> > >> >> Marvin Scholz <epirat07-at-gmail.com@ffmpeg.org> 于2025年7月9日周三 03:14写道: >> >> Hi Marvin, >> >> >> >>> >> >>> The use of this protocol was already discouraged and warned about >> >>> for years with the recommendation to use the HLS demuxer instead. >> >> What about make deprecated warning to users and remove it next major version? >> > >> > You mean change the discouraged to deprecated? We could do that but IMHO >> > the previous message was quite clear it shouldn't be used anymore. >> > >> > But I don't mind waiting another year for this till next major >> > bump after 8.0, if thats what people prefer. >> >> I didn't even know this existed. Specially with that message, it seems >> fair game to me to just remove it. > > > I'm aware of the existence of hls proto, but I'm not a user of it myself. Removing it wouldn't affect my ability to use HLS functionality. However, I'm uncertain whether other users might still be utilizing hls proto. > > Judging from the persistent warning messages associated with hls proto, it doesn't appear that users are being explicitly warned about its deprecation or impending removal. It's possible that some users who only require basic HLS capabilities might still be relying on it. > > Therefore, I believe it would be reasonable to either mark it for removal or explicitly deprecate it. That said, directly removing it wouldn't impact me personally. I now realize 'discouraged' is essentially signaling deprecation, nudging users toward the hls demuxer alternative (via direct m3u8 URLs) unless problems arise. 😂 > >> _______________________________________________ >> ffmpeg-devel mailing list >> ffmpeg-devel@ffmpeg.org >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel >> >> To unsubscribe, visit link above, or email >> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-07-10 0:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-08 19:14 Marvin Scholz 2025-07-08 20:59 ` Martin Storsjö 2025-07-08 21:01 ` Marton Balint 2025-07-09 9:18 ` Steven Liu 2025-07-09 13:28 ` Marvin Scholz 2025-07-09 15:32 ` Timo Rothenpieler 2025-07-09 20:42 ` Steven Liu 2025-07-10 0:43 ` Steven Liu [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CADxeRw=QrNitNFWE1go5SXAFvPhQbMYNG9iwvqxn4GWYYSSZ1Q@mail.gmail.com' \ --to=lingjiujianke-at-gmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git