Comments on: The Everything and Nothing WebRTC Vendor Syndrome https://bloggeek.me/webrtc-vendor-syndrome/ The leading authority on WebRTC Sat, 02 Jul 2022 17:10:51 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/webrtc-vendor-syndrome/#comment-117667 Mon, 15 Dec 2014 08:12:54 +0000 http://bloggeek.me/?p=8929#comment-117667 In reply to Sandro Parisi.

Sandro,

I am not sure where you are going with this line of thought. For the apparent foreseeable future, no single vendor can provide all the answers to all the customers. But how does that even relate to detecting browsers and devices?

]]>
By: Sandro Parisi https://bloggeek.me/webrtc-vendor-syndrome/#comment-117666 Mon, 15 Dec 2014 07:55:18 +0000 http://bloggeek.me/?p=8929#comment-117666 The truth is that none WebRTC solution will address all the requests that a customer might have. Transparency, full browser compatibility, simple porting on mobile devices, …

This is why is needed a solution that can be used in this different scenario, with the capability to detect the browser/device and define the best protocol to use.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/webrtc-vendor-syndrome/#comment-117665 Mon, 08 Sep 2014 10:17:01 +0000 http://bloggeek.me/?p=8929#comment-117665 In reply to hanumesh.

That’s thinking small. There are a lot of things that WebRTC doesn’t and won’t bring out of the box. Things like multipoint support, recording, etc.

My focus (and to some extent rant) here is about the promised features from a vendor and not from the adoption of the technology itself.

]]>
By: hanumesh https://bloggeek.me/webrtc-vendor-syndrome/#comment-117664 Mon, 08 Sep 2014 10:12:50 +0000 http://bloggeek.me/?p=8929#comment-117664 The day when WEBRTC is stable on all browsers , it will be everything syndrome

]]>