This would be at Oracle, I'm assuming.
PubSubHubbub?
--
M. Edward (Ed) Borasky
http://borasky-research.net
Pondering the pandemonium of pontificating and pandering to ponderous
pandas since 1999
But I tend to think of it as a pub inside a submarine!
The hubbub one experiences at a pub inside a submarine makes a lot of
sense. Subs ping and ecolocate, much like we do with RSS. Also, we
drink while we do this, especially at Beer and Blog, where our RSS
constructs do our heavy social sensing work for is. So if we're all
ecolocating and pinging things, that makes our computers subs, and our
social interactions pubs, and the rusulting hubbub of that is
PubSubHubbub! (Thanks to Ed for the CamelCasing).
Put simply, PubSubHubbub is a pubsub (Publisher–Subscriber) messaging
protocol that extends the ATOM/RSS model (this was what “RSS 2.0” was
supposed to be, if you catch my drift.) This makes it really pertinent
to the Data Plumbing user group.
PubSubHubbub solves the real-time delivery problem (“I want the news
_right_ now” or how about “I want my lifestream to be delivered to my
friends right at this moment”) by making every ATOM or RSS file
declare a hub server.
You, as a reader, would subscribe to this hub server (the idea is
obviously to have these servers be run in a distributed and localized
manner.)
By making publishers declare a hub, subscribers can then avoid doing
the whole “asking the server directly” or “pull” action every few
minutes, which is a drain for the publisher’s server because they have
to go “no, there is nothing new” over and over again.
Instead, PubSubHubbub works by ways of “push”. Okay, we have this hub
server; so the next time a publisher post a new item, he will ping
this hub and say “hey, here’s a new item for”, and then the hub could
say “okay, thanks, now I will distribute it to all of your
subscriber’s client.”
No pulling teeth, faster delivery (well, theoretically) and everyone
is happy.
I will start putting this in my email signature. Just you wait.