Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
1–10 of 51 posts
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#2For those interested in Google's implementation:
https://code.google.com/p/webrtc/source/browse/#svn%2Ftrunk%...
or browse the code:
svn checkout http://webrtc.googlecode.com/svn/trunk/ webrtc-read-only
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#3For those interested in Google's implementation: https://code.google.com/p/webrtc/source/browse/#svn%2Ftrunk%... or browse the code: svn checkout http://webrtc.googlecode.com/svn/trunk/ webrtc-read-only Also Ericsson's code is on github (I couldn't find a direct link from the parent article): https://github.com/EricssonResearch/openwebrtc/
Great Thanks !
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#4Given that they're both open source, built to the same open standard, and (at least nominally) completely interoperable, I'd say "complement" would be a better word than "rival."
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#5They open it after all the other browser vendors are already done with this task. Why haven't they released it from the very beginning, saving a few days work-time for others?
I think that now it has almost zero value.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#6Great to see Ericsson open sourcing awesome stuff.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#7One of the biggest issues in the whole WebRTC process has been getting companies to commit to documenting the minimum SDP for interop. I'm curious how well these two implementations will interop. One of the reasons for ORTC is to remove signaling from the specification.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#8Given that they're both open source, built to the same open standard, and (at least nominally) completely interoperable, I'd say "complement" would be a better word than "rival."
It is generally considered a positive thing when proposed standards have multiple independent implementations.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#9They open it after all the other browser vendors are already done with this task. Why haven't they released it from the very beginning, saving a few days work-time for others? I think that now it has almost zero value.
I think there's a significant amount of value in having multiple independent implementations, especially when they are open-sourced and can borrow from as well as compete against each other. See, for example, OpenSSL/LibreSSL/GNUtls.
Re: Ericsson open-sources OpenWebRTC, rival to Google’s WebRTC implementation
#10They open it after all the other browser vendors are already done with this task. Why haven't they released it from the very beginning, saving a few days work-time for others? I think that now it has almost zero value.
The README states the focus isn't on browsers
> OpenWebRTC is built on the belief that the WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem
and it has out of the box platform support for iOS and Android