We all understand the general idea behind WebRTC technology and its intent – however, it’s fair to say that defining WebRTC applications can be a fairly complex process. The logical solution would be to check the standard – however, the IETF and W3C groups that are working to approve the WebRTC standard have not yet agreed on it – and debate about the technological components is ongoing.
Despite this clear lack of formal identification, many WebRTC solutions are already available – partly due to input from Google who released libraries of codecs and transports to back up their own interpretation of WebRTC support within the Chrome browser, modeled after a proposed WebRTC standard.
A recent article by nojitter.com explores WebRTC applications further – and the debate surrounding the likely components. The article reaffirms that scale and interoperability continue to be important challenges across all forms of communication; however, technology protocols can help to make communications easier. This in turn will support take-up and change peoples’ habits – leaving the debate around how best to focus on the end-user experience and the need to be ready to support standards from a CSP or infrastructure partner focus…
…which leads us to CAPEX vs. OPEX expenditure – build with OPEX using SmartIPX as your partner and focus on what you are good at – servicing your customers!
Read the full nojitter.com article here: http://www.nojitter.com/post/240168993/whats-a-webrtc-application