The latest blog innovation is how RSS interacts with subscribers. This round of innovation is push instead of pull. The way RSS has worked is that the RSS client will pull the website each time, asking if there were any updates. PubSubHubbub changes that. Instead of asking, it’s now told.
This video explains it really well.
So how does this impact you?
For WordPress.com bloggers, you don’t have to do anything; you already have it. For self-hosted blogs, like WordPress Vibe, you can download the plugin to get the same functionality. It’s being termed as “PuSHPress.”
Will PuSHPress be integrated into the core of WordPress?
In a simple response, “..staying a plugin, most likely” — Automattic Engineer, Ryan Boren
Here’s a quick recap of what this new functionality will offer.
- An feed URL (a “topic”) declares its Hub server(s) in its Atom or RSS XML file, via . The hub(s) can be run by the publisher of the feed, or can be a community hub that anybody can use. (Atom and RssFeeds are supported)
- A subscriber (a server that’s interested in a topic), initially fetches the Atom URL as normal. If the Atom file declares its hubs, the subscriber can then avoid lame, repeated polling of the URL and can instead register with the feed’s hub(s) and subscribe to updates.
- The subscriber subscribes to the Topic URL from the Topic URL’s declared Hub(s).
- When the Publisher next updates the Topic URL, the publisher software pings the Hub(s) saying that there’s an update.
- The hub efficiently fetches the published feed and multicasts the new/changed content out to all registered subscribers.
Popularity: 4% [?]
Related posts:
