« Next Document: Reference Architecture For Social Network Sites | Main | Leveraging Employee Social Networks »

July 16, 2008

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d834515a5969e200e553a241878833

Listed below are links to weblogs that reference IM Standards: Vendor's Are In A Different Reality:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Dave Uhlir

No whining here from Jabber, Inc.!

As you point out, we are deeply involved in multi-protocol federation.

It is not how many protocols are used, but how open they are. There is a big difference between federation between systems using open, documented protocols versus proprietary, undocumented protocols and extensions. In the open case, it is clear what needs to be done. Federating with closed systems requires considerable guesswork and trial and error.

Ultimately, the market will resolve this issue. From a risk management standpoint, customers should be skeptical of products and systems designed around proprietary protocols. Vendor lock-in through proprietary standards has become repellent in many parts of the IT industry. As presence and real-time messaging continues to gain in importance, IT decisionmakers are likely to start resisting solutions based on closed protocols.

The comments to this entry are closed.

Become a Fan

Twitter Updates

    follow me on Twitter