For the sake of clarification I replaced the verb "poll" with "retrieve" in (I think) the area you are concerned with. The usage was in the context of polling a feed (once) upon receipt of a notification it had been changed. Seems like a valid common use case - at least in the circles I run in. It was not intended to refer to frequent polling to a schedule.
I also searched the article quickly, but only found an innocent use of the same verb in the exact same context, completely unrelated to rssCloud. The choice of the original verb was not a conscious decision, so I will not be referring to the thundering herd issue. I also fully understand both specifications. Feel free to point out any similar corrections - more than willing to make the alterations. Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Matthew Terenzio <[email protected]> To: [email protected] Sent: Fri, October 16, 2009 9:38:40 PM Subject: [pubsubhubbub] Re: Article: Pubsubhubbub And PHP - Part 1: Pubsubhubbub Introduction, Contrast With rssCloud, And Simple Publisher Implementation I think it might help the community to stop saying that PubSubHubbub eliminates the need for polling while rssCloud does not. That just simply isn't true. Polling is what RSS or Atom does when their is neither PSHB or rssCloud. rssCloud merely makes a "request" upon being pinged. No ping, no request. Please don't come back with more about thundering herds. I fully understand both specs. I'm not trying to make a statement about whether one spec is better or not, just addressing the mistaken use of the term polling. I've seen it more than once and it may confuse the less technical people trying to understand these things.
