Will, Thanks for clarifying. I was so happy I could (somewhat) answer a question I jumped the gun a bit. ;)
andy On Sat, Mar 6, 2010 at 1:14 PM, Will Norris <[email protected]> wrote: > to be clear, the publisher simply pings the hub that new content is > available. This is a simple POST with a couple of parameters... it's not a > "fat ping", like what you (may) have when the hub delivers the content to > subscribers. But yes, in order to actually get things to near real-time, > the publisher has to either be a hub itself, or ping a separate hub as soon > as new content is available. > -will > > On Sat, Mar 6, 2010 at 11:33 AM, Andy Ennamorato <[email protected]> > wrote: >> >> Correct - publisher (rss provider) has to push to a hub. >> Note that wordpess.com/.org just enabled this in their blogs, and I >> imagine other blog/rss frameworks will add similar plugins or features soon. >> >> Andy >> >> Sent from my iPhone >> >> On Mar 6, 2010, at 3:20 AM, ED209 <[email protected]> wrote: >> >>> Hi all, >>> such a great initiative, really like the concept. I have one question >>> though which I can't seem to find a direct answer to. Does >>> pubsubhubbub hang on the fact that the source website has implemented >>> these push notifications? i.e. pubsubhubbub wouldn't work on an type >>> of rss feed e.g. >>> http://www.artflock.com/artist/lakeillustration/artwork-rss/ >>> ? As per this example artflock.com would have to implement >>> Pubsubhubbub in order to get instant updates? >>> >>> Thanks :) >> > >
