Earlier this week, Google
shared its plans for the future unification of the instant messaging (IM) market. The benevolent overlord of modern Internet innovation, Google has become a tremendous stabilizing force within the complex ecosystem of web-based services. When Google
released their Jabber-based IM
application earlier this year, they promised consumers that they would vigorously pursue protocol interoperability in order to facilitate communication between users of different IM systems. Since the birth of text-based Internet chat in the 1980s,
countless IM protocols and applications have emerged to meet the rapidly growing demand for interactive text communication. AOL's ubiquitous AIM service is thought to have over 50 million active users, a number that continues to increase as more consumers take up the habit.
Google chose to use Jabber's Extensible Messaging and Presence Protocol (XMPP) for its own Google Talk application because XMPP is a well-documented open protocol fit for standardization and extension. The broad availability of XMPP support in open source communication applications ensures that users of all common platforms, including Linux and OS X, will be able to interact with Google Talk users. Working closely with the nonprofit Jabber Software Foundation (JSF), Google plans to bring voice and video communication services to all XMPP-compliant IM utilities. Described in a Jabber Enhancement Proposal, the new peer-to-peer voice and video standard is currently called Jingle. An open source implementation called
Libjingle has already been released by Google under a BSD-style license. For those not in the know, BSD licenses are very permissive, facilitating commercial redistribution even in proprietary applications, which means that closed source IM applications like AOL's AIM client can take advantage of the code.
___________
Source:
Ars Technica
Dec 25, 2005, 11:05 PM
