|
|
|
|
|
|
by TD-Linux
3253 days ago
|
|
|
>Fist of all it is not designed for server-client cases. WebRTC is specifically designed for server-client cases. In the case of video and audio, the server is called a "mixer" or MCU. This is extremely important for large multi-user conferences - if it weren't for a mixer, you'd have to upload your video once for every user, burning all of your upload bandwidth. Examples of services using this are Appear.in Premium and Cisco Spark. Note that games are the #1 use case mentioned in the Datachannel draft [1]. It's perfectly fine to argue that the standard is bad, but it was designed for these use cases. The Google developer you linked seems to be arguing for improving the WebRTC C++ library, not changing the protocol. [1] https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-1... |
|
|