This link has been bookmarked by 76 people . It was first bookmarked on 20 Apr 2009, by John Keyes.
-
François Parmentier"A simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom and RSS. "
-
Chaim KrauseA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom and RSS.
Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated. -
Pascal MolliNot already tagged pubsub ?
-
-
reference implementation
-
publish/subscribe
- 11 more annotations...
-
-
anthonastromveeery interesting..!
-
wolf hessepubsubhubbub
-
yuppi cA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom and RSS.
Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated. -
RuudParties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated
-
tosh .A simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom (and RSS).
Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated.
The protocol in a nutshell is as follows:
* 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.
The protocol is decentralized and free. No company is at the center of this controlling it. Anybody can run a hub, or anybody can ping (publish) or subscribe using open hubs.
To bootstrap this, we've provided an open source reference implementation of the hub (the hard part of the protocol) that runs on Google App Engine, and is open for anybody to use. -
Dirk Jende-Holzmannsimple, open, server-to-server web-hook-based pubsub
-
Yasuhito TakamiyaRSS の更新を従来の polling から push にすることで、 twitter 並みの短いタイムラグでの通知を可能にする技術
-
-
The protocol in a nutshell is as follows:
-
-
kaspar_ruA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom (and RSS).
-
-
An feed URL (a "topic") declares its Hub server(s) in its Atom or RSS XML file, via <link rel="hub" ...>.
-
avoid lame, repeated polling of the URL and can instead register with the feed's hub(s) and subscribe to updates.
- 1 more annotations...
-
-
Mark BlairA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom.
Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (Atom URL) they're interested in is updated.
The protocol in a nutshell is as follows:
* An Atom URL (a "topic") declares its Hub server(s) in its Atom XML file, via <link rel="hub" ...>. The hub(s) can be run by the publisher of the Atom, or can be a community hub that anybody can use. (RssFeeds are also 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.
The protocol is decentralized and free. No company is at the center of this controlling it. Anybody can run a hub, or anybody can ping (publish) or subscribe using open hubs. -
Srinivasan VA clear and concise intro on pubsub....
-
Maluvia HaseltineA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom. )
Like Twitter for RSS feeds? -
François CharoyA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom.
-
Tristan RivoallanA simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom.
-
John Keyes__Pubsubhubbub__ is a simple solution to feed polling strangulation problem.
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.