Google has just released a set of components called Libjingle that allow third party applications to interact with Google Talk. The components, which include some source code, are being released under a very liberal license allowing for free incorporation into commercial and non-commercial software.
We are releasing this source code as part of our ongoing commitment to promoting consumer choice and interoperability in Internet-based real-time-communications. The Google source code is made available under a Berkeley-style license, which means you are free to incorporate it into commercial and non-commercial software and distribute it.
In addition to enabling interoperability with Google Talk, there are several general purpose components in the library such as the P2P stack which can be used to build a variety of communication and collaboration applications. We are eager to see the many innovative applications the community will build with this technology.
Below is a summary of the individual components of the library. You can use any or all of these components.
* base – Low-level portable utility functions.
* p2p – The p2p stack, including base p2p functionality and client hooks into XMPP.
* session – Phone call signaling.
* third_party – Non-Google components required for some functionality.
* xmllite – XML parser.
* xmpp – XMPP engine.
Google has done a great job with spurring Google Maps mashups – some people claim hundreds of thousands of third party applications. This code release is even more important and is a huge end around Skype. In fact, Google has basically put a gun to Skypes head and demanded they now release their API as well.
Skype allows integration with the Skype client. What Google has done goes far beyond this, allowing integration with the Google Talks VOIP network.
Heres an example of a potential mashup – putting google map location information in the same application as google talk, allowing mapping of everyone in the conversation (Gizmo does this). See local businesses and people and add them to the conversation. [TechCrunch]