Pubsub Adoption


The other day Piers Harding asked me why XMPP publish-subscribe technologies haven't taken off yet. Since Piers was at the 2002 meeting in Munich where we had some lengthy discussions about pubsub, he knows that pubsub has long been a contentious issue (e.g., it took us a long time to make peace between those who wanted to do event notifications only and those who wanted to persist items for later retrieval).

Here are some possible reasons:

  1. Pubsub is not an IM technology -- and we have a hard enough time getting client and server developers to implement those!
  2. The basic concept behind pubsub is simple, but the spec is long and complicated because there are so many optional features and alternate flows in the use cases. I've tried to simplify the spec and will put some more work into that over the next week or two (e.g., by adding a friendly "How It Works" section).
  3. There still is no "killer app" for pubsub. Possible applications include real-time RSS feeds (actually Atom) and social presence à la Twitter and Jaiku.

I suppose we were ahead of our time by working on pubsub back in 2001 and 2002. But that's not uncommon. As I like to put it, we build the runway and we make it as long and smooth as we can; what kind of aircraft you build and where you fly the plane are up to you. :)

Peter Saint-Andre > Journal