Google touts real-time RSS transplant
What's all the PubSubHubbub?
Web 2.0 NY Google is trumpeting a new messaging protocol it insists on calling PubSubHubbub.
Brett Slatkin - a software engineer on Google’s App Engine team - demonstrated the protocol this week at the Web 2.0 Expo in New York. It aims to turn RSS and Atom into real-time content delivery mechanisms - and maybe even revamp Google search.
In a traditional RSS or Atom implementation, there's a publisher, and there's a subscriber. The subscriber polls the publisher for updates, and if publishers has an update, it pushes it down the pipe. As Slatkin explains, this can be costly for organizations posting content. It results in heavy traffic from subscribers polling for content, and there's unnecessary bandwidth eaten up with each push. Entire feeds are sent to subscribers, not just the changed.
And since the subscriber has the responsibility of requesting new content, RSS feeds aren’t updated in real-time. New content is only available once it's been requested. Say, for instance, a site has an RSS feed embedded on the homepage. New posts to that feed won’t instantly appear on the site where the feed is embedded.
Simple in nature, PubSubHubbub relies on hubs and differentials to transform RSS and Atom feeds into real-time updates and significantly reduce the amount of bandwidth used.
A publisher signs up with a hub provider, and the feed sent to subscribers includes a declaration that points the user to the hub address, telling them the hub is a trusted entity. At that point, the subscriber has the option to subscribe with the hub for real-time delivery.
Whenever the publisher adds new content to the feed, the feed is sent to the hub. The hub, in turn, looks for differences in the feed, removes the content that the subscriber has already received, and multicasts a partial feed that includes just the new content to subscribers.
Because this is designed to work with RSS and Atom, publishers don’t have to implement new solutions. They can continue to use their existing feeds for instant syndication.
A publisher can also deploy its own hub. In this way, Slatkin explained, a publisher can create a system where it pushes out the content on its own in real-time to subscribers whenever content is published.
Sponsored: What next after Netezza?