From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/http: Add max_request_size option
Date: Sat, 14 Jun 2025 11:27:42 -0500
Message-ID: <CAAhd_PXQDr6EFEAT4vt5-8DACweFVB27PhAYsPAbenQuBJjEjA@mail.gmail.com> (raw)
In-Reply-To: <99c58974-aba6-4c4f-8530-9bbcb7811634@fratti.ch>
Hello, bringing this back from the grave.
Nicolas Frattaroli:
> if I'll change it to anything then maybe max_requested_size, but
> max_range_size seems less clear to me because that it does this through
> the range header is not relevant to the user, its effect is, which is
> that FFmpeg requests less data per sent request.
I align with your logic about naming toward the effect, and
max_requested_size makes sense.
As for the concurrency concern, can you help me understand it a bit
more with an example?
In this way I can research it (or if there are any SMEs please step in).
Zhao's statement about potential server flooding is also valid.
If there's strong opinion from others there I think its worth to hear.
In my eyes someone can accomplish the same effect with changing header
values directly or using curl.
It my also be for legitimate reasons.
Thank you all,
Marth64
_______________________________________________
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".
parent reply other threads:[~2025-06-14 16:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <99c58974-aba6-4c4f-8530-9bbcb7811634@fratti.ch>]
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=CAAhd_PXQDr6EFEAT4vt5-8DACweFVB27PhAYsPAbenQuBJjEjA@mail.gmail.com \
--to=marth64@proxyid.net \
--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