why youtube use quic & dash &hls instead of webrtc (protocol)

[Philip Yoon]

Why does Google use another protocol instead of webrtc on YouTube? Webrtc also has some cool features like other protocols, so why not use webrtc?

is anybody know the answer?

[Ian Swett]

WebRTC is designed for realtime communications, whereas DASH and HLS are designed for large scale video delivery.  In particular, HTTPS is much easier to scale up to a large number of users than WebRTC.

On Mon, Jun 11, 2018 at 3:32 PM Philip Yoon <asgu...@gmail.com> wrote:

Why does Google use another protocol instead of webrtc on YouTube? Webrtc also has some cool features like other protocols, so why not use webrtc?

is anybody know the answer?

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Luca De Cicco]

Hi Philip,

as Ian said, DASH employs standard HTTP servers and caches to scale to potentially millions of concurrent users. DASH is typically used in scenarios such as Video on Demand (VoD) and LiveTV scenarios where latencies have a lower impact on QoE with respect to other metrics. 

Cheers,

Luca  

[Philip Yoon]

Thank you for your reply.
Could you give me one more answer?
Why does https accept more users than webrtc?

[simonpiet...@gmail.com]

Hi,

I am really curious why HTTPs should scale better than WebRTC. Do you have figures/scenarios backing this statement up, which you can share? 

Thanks,

SImon

Simon 

Inviato da iPhone