4 comments on “What is a WebRTC Gateway anyway? (Lorenzo Miniero)

  1. You are saying:
    “You may, of course, just take the Chrome stack and start it all from there. As I anticipated, a gateway is, after all, a compliant WebRTC implementation, and so a complete codebase like that can definitely help. For several different reasons, I chose a different approach, that is trying to write something new from scratch”.

    Can you share what the reasons are?
    WebRTC standard is evolving all the time. Is not it easier to derive your code from the Chromium native implementation? If there are WebRTC standard updates, Chromium implementation should reflect it much sooner than any other code base.

    • That’s one way to go. It may be debatable on whether or not it’s better to start from their stack or not. I preferred to implement it from scratch to have absolute control on the overall process, rather than spending weeks to study their code to understand where I could safely put my hands, with the risk of getting lost again after an update. Besides, having different implementations in place is good for the standards, otherwise you only get a bunch of Chrome instances wearing different dresses talking to each other 🙂

  2. I agree that the implementation of webrtc protocol standards update might affect the previos working version on certain browsers.

    When any service provider or Enterprise who want to make their SIP infrastructure WebRTC enabled then they must use a WebRTC- SIP Gateway.

    As there might be myriad of use cases using webrtc, both on web and mobile, keeping track of new updates in an ongoing task to manage 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *