Can anyone explain please, whether WebRTC is a protocol or not? After reading this: http://www.webrtc.org/faq#TOC-Why-should-I-use-WebRTC- I thought it's just an API to enable other protocols (XMPP/Jingle, SIP etc.) to be built through JavaScript. Or is it a protocol after all?
I'm also a bit curious about the protocol part, found this tidbit on their site "The session components are built by re-using components from libjingle, without using or requiring the xmpp/jingle protocol." (http://www.webrtc.org/reference/architecture#TOC-Transport-S...)
Comments
Can anyone explain please, whether WebRTC is a protocol or not? After reading this: http://www.webrtc.org/faq#TOC-Why-should-I-use-WebRTC- I thought it's just an API to enable other protocols (XMPP/Jingle, SIP etc.) to be built through JavaScript. Or is it a protocol after all?
I'm also a bit curious about the protocol part, found this tidbit on their site "The session components are built by re-using components from libjingle, without using or requiring the xmpp/jingle protocol." (http://www.webrtc.org/reference/architecture#TOC-Transport-S...)
I think this is a really nice overview for WebRTC: http://www.html5rocks.com/en/tutorials/webrtc/basics/ There is a section around standards and protocols.