PubSubHubbub for Google alerts: a small real time step

Thu 20 August 2009 11:02, Editors

PubSubHubbub for Google alerts: a small real time step

Google wants to make the web programmable because the one application can be extended by another to create new applications. That is how they open their post on the Google code blog. In this post they explain how they enabled #v144# for Google alerts.

With the enabling of this protocol developers can " write web applications that process newly relevant search results as they become available". Roughly translated: Google alerts can now send notifications real time.

The PubSubHubbub-protocol (who ever came up with that name?) is not just about mash ups. It's more advanced. Google for example gives the Wave Robots API as an example of a wat to give "developers the power to enhance and modify the behavior of Wave in new ways that no-one has envisioned."

The protocol "provides web-hook notifications when Atom and RSS feeds are updated, delivering web applications near-real-time information about what's new or changed" and is open source. Simply stated: it speeds up the time it takes to get a feed found by several sources.

Think of it as an AJAX search API that tells *you* when it finds new results. Acting upon these notifications your app could update your website, email friends, send an SMS — the possibilities are endless,” Google states on the code blog.

The protocol in a nutshell according to Google:

  • An feed URL (a "topic") declares its Hub server(s) in its Atom or RSS XML file, via <link rel="hub" ...>. 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.

In the last weeks Google already added the protocol to other Google services like FeedBurner, Reader shared items and Blogger.


  • Comments (0)
  • Google
  • Tell-a-cowboy

Comment

  • HTML is not allowed. URLs are automatically clickable.
    * Email address is not shown



  • Google Nose
  • Flight Search
  • Flight Search
  • Ingress
  • Google Handwrite
  • Using Google search
  • IPv6 launch
  • Not going to miss the internet

Last Comments


Events

Last event

Bloggers

  • J-P De Clerck
    J-P De Clerck

    Profession: Customer-centric digi...

    Company: Conversionation

  • Sam Murray
    Sam Murray

    Profession: Senior Search Consultant

    Company: Verve Search

  • Susie Hood
    Susie Hood

    Profession: Head of Copywriting

    Company: Click Consult / SEO C...

  • Tom Bogaert
    Tom Bogaert

    Profession: Managing Partner

    Company: QueroMedia


Latest Videos

Border_top
Border_bottom

Columns

  • Lizette van der Laan
    Social Media Image

    Is it the real you, the witty you, the person who reads the most interesting articles, makes t...




Newsletter

Subscribe to SC Newsletter:


RSS Feed

Are you a bloggerFacebook


Search



© 2014 Searchcowboys.com - All Rights Reserved - All views and opinions expressed are those of the authors of Searchcowboys.

All trademarks, slogans, text or logo representation used or referred to in this website are the property of their respective owners. Sitemap