Jabber transports and reliability

There is an open letter up on the Cocinella website about why IM clients which come bundled with support for multiple protocols are actually bad for interop.

I actually agree, but the problems listed about using transports as the solution are not merely theoretical.

I have been a Jabber user for more than six years and I have not found a single remotely hosted transport that I can rely on for the critical task of actually communicating with other people.

As far as I’m concerned, jabber.org should be hosting the most reliable transports on the planet and then making sure that other servers who want to run them can do so in a reliable way. There is nothing more likely to turn someone off than the promise of practical cross-protocol support turning out to be nothing more than wishful thinking.

Published by

5 thoughts on “Jabber transports and reliability”

  1. I think that article’s bobbins to be honest.

    As you say, the transport’s are hopelessly unstable and even if they were improved they are still just another point of failure.

    It’s also totally unclear how transports solve his lowest common denominator problem. If you want to support some service above this the client will still need to know the capabilities of the person they are talking to.

    If I were a client author even though the effort might be bigger I’d probably want to have the protocol code in my control and not in some external project that I am not part of. If MSN breaks something suddenly, I now need to make sure this other project makes a fix and release. I then have to hope that this release is rolled out in a timely manner to the servers that run the transport.

    Similarly as an end user, when a protocol breaks, it’s clear with a multi protocol client where to go for a fix. With the transport system I have to hunt around for a server that’s installed the latest transport.

    Thanks, but no thanks.

  2. Google are using jabber protocol for their google talk. They have a client
    and I think it is possible to configure other clients to use their system
    if you want to talk to other people on google.

    Because it’s for google users it isn’t the solution for everyone, unless
    we all register with google.

    I guess they take the code and make it their own, and will update when
    they update their client, making sure not to break anything.

  3. Yes they are, and yes it is possible, but it doesn’t matter in this context because they’re running a Jabber-only server, not running any transports.

    Unless that’s not your point?

  4. Yes but I got so confused when writing.

    Like said in a different tread, the best solution would be to change the people.

  5. “As you say, the transport’s are hopelessly unstable and even if they were improved they are still just another point of failure.”

    It’s no additional point of failure compared to multi-protocol clients.

    Anyway, I believe a big company like Google could drastically improve the situation by providing stable transports…preferably open-sourced of course.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.