The big news out of Google this week was their support of XMPP-Jingle as the “primary signaling” protocol for Google Talk calls to and from Google, iGoogle and Orkut. From the announcement by Peter Thatcher (my emphasis added):
We are pleased to announce that we have launched support for Jingle XEP-166 and XEP-167 for Google Talk calls to and from Gmail, iGoogle, and Orkut. We have also added the same level of support to libjingle (http://code.google.com/p/libjingle), which is used by many native clients. From this point on, it will be our primary signalling protocol, and the old protocol will only remain for backwards compatibility.
and further down:
But the future is Jingle, and the old protocol will eventually go away.
This is obviously a huge endorsement for XMPP – and the XMPP Standards Foundation (XSF) naturally had a post up on the topic.
Now, this is not a “surprising” move because Google has been very involved in the development of Jingle and, as noted by the XSF, Google’s original Google Talk VoIP protocol was a precursor to Jingle. Still, it’s great for Jingle to have the formal endorsement – and perhaps more importantly, the deployment – of Google. The XSF note also points out how this usage by Google can lead to improved interop and more developers using Jingle.
Of course, the obviously question asked by some out there, including in the Hacker News discussion thread, was: why not use SIP?
The truth is that while SIP is an excellent protocol for so many use cases, there are some situations where it’s not the best… and where in this case XMPP-Jingle is a better choice.
We’ve seen that choice here within Voxeo. While we are a HUGE user of SIP – and have our giant SIP cloud sitting out there hosting applications – when we created our Phono SDK to let people easily build voice and IM clients directly in a web browser, we chose to use XMPP-Jingle for part of the path. You can see that in our Phono architecture post:
Why did we use XMPP? Low latency, firewall-friendly… and also with the necessary IM and presence support. It was a lot easier to implement that inside a browser versus a full-blown SIP stack.
It’s great to see Jingle getting this kind of support from Google … and we’re looking forward to seeing increased Jingle usage out there.
Posts by others:
- XMPP Foundation: Google: “The Future is Jingle”
- Hacker News discussion thread on this topic
- Tom Keating: Google Talk Adopts Jingle As Default VoIP Protocol
- Digitizor: Jingle Becomes The Default Protocol For Google Talk’s VoIP