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-requ...@ffmpeg.org with subject "unsubscribe".
