[vlc-devel] [PATCH] RFC: http: add support for byte range requests

[Rémi Denis-Courmont]

Hi,

There is no explanation why this is needed, and how this won't hurt performance badly where it's used, or make things more complicated for no benefits.

I don't disagree that this won't affect normal HTTP streaming, and that's not the point.

Le 17 juin 2019 09:23:19 GMT+03:00, Thomas Guillem <thomas at gllm.fr> a écrit :
>hi,
>
>On Sat, Jun 15, 2019, at 07:53, Rémi Denis-Courmont wrote:
>> 	Hi,
>> 
>> Streaming in ranges breaks pipelining and cannot work properly if the
>RTT is 
>> non-negligible. Sequential streaming must use a half-open range.
>> 
>> Likewise multi-track (like AVI) streaming needs to use multiple
>half-open 
>> ranges in parallel, in other words, multiple streams - and that is
>not specific 
>> to HTTP at all.
>
>Range request will be only used for adaptive, why are talking about
>.avi ?
>
>> 
>> New stream must only be used when unavoidable - notably when seeking
>or 
>> getting a different resource (e.g. rate switch).
>> 
>> This patch has zero rationale. Nack.
>
>This patch doesn't change the actual http access behavior. This new
>function will only be used by adaptive in order to refactor *a lot* of
>code.
>
>I really don't understand your refusal ? Could you explain what should
>be done then ?
>
>> 
>> -- 
>> Rémi Denis-Courmont
>> 
>> 
>> _______________________________________________
>> vlc-devel mailing list
>> To unsubscribe or modify your subscription options:
>> https://mailman.videolan.org/listinfo/vlc-devel
>_______________________________________________
>vlc-devel mailing list
>To unsubscribe or modify your subscription options:
>https://mailman.videolan.org/listinfo/vlc-devel

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20190617/c2b8c80e/attachment.html>