Re: [quicwg/base-drafts] Possible HoL blocking due to co-mingling payload and metadata (header) address space. (#1606)

[grmocg <[e-mail]>]

Http has explicit control for caching, scales to millions, and is already
in use by the application (e.g. for getting the list of videos, thumbnails,
etc), which would otherwise have to deal with contention between multiple
connections (something which decreases the accuracy of the bandwidth
estimate, and would cause rebuffering if not controller for).

Http offers a mechanism (via byterange requests on named resources) to
'heal' uploads/broadcasts if there should be an interruption, reconnection,
server restart,

Http offers all of the semantics we want except partial reliability, which
is what this is about!

On Wed, Jul 25, 2018, 6:33 PM ianswett <[e-mail]> wrote:

> Q: What's the benefit of HTTP here? It seems like you might want RTP
> and/or WebRTC over QUIC?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1606#issuecomment-407947737>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA9dcqPcNXi-fGrADGIXqPjlMsVx4n10ks5uKRxugaJpZM4VgyRs>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1606#issuecomment-407951495