Thanks for the responses Jeff. Have moved further, and have successfully registered a callback+topic combination. The "Get Info" button on http://pubsubhubbub.appspot.com/subscribe also shows that the subscription is valid for 30 days from now.
The topic(feed) is actually a blog hosted on blogspot.com and I've added 4 new entries in the past 2 hours but no POST requests to the callback URL yet. What's a reasonable timeframe to expect them? Just need to complete one fully cycle of subscribe, get notified, process further before I can commit myself to using PSH. Thanks in advance, Alok On 8 जन, 22:49, Jeff Lindsay <[email protected]> wrote: > Allow me to take a stab... > > > The question is: What prevents a feed publisher from drowning the hub > > or me (the subscriber) with multiple updates - maybe thousands per > > second? (In real life, such things happen, you know - at least in my > > life they do :) ) Can the subscriber set a limit to the number of > > callbacks it wants to receive in a time frame? Or any other way that > > may have been thought of of "solve" this problem. > > > Basically I'm a little uncomfortable with losing control over when to > > ping - but am still interested because of the enormous band width and > > cpu savings of course. > > Think of your callback URL like a webpage ... you can't really control how > hard it's hit (hence slashdot effect, etc). You can add rate limiting in > front of it if you're really worried. So a) don't subscribe to publishers > you don't trust to not flood you, b) deal with it appropriately as HTTP if > they do and you still want to subscribe to them. > > I don't think it's the hub's responsibility. > > > > > Question 2. > > Verify type - Synchronous/asynchronous - what verification is this? I > > tried to look for documentation but couldn't find any. Maybe I was > > looking at the wrong places so any pointers would be appreciated. Yes, > > the code would tell me, but currently am trying to use this as a > > "user". > > To verify with the callback that it wants to receive updates. > > > > > Question 3. > > Verify token - what is this for? Is it the same verify as "Verify > > type" above? > > This is basically for your own verification purposes. It's not necessary. If > specified it will be passed in the verification step mentioned above. > > > > > Question 4. > > HMAC secret - being optional, what does a subscriber stand to lose if > > it's not specified? > > Basically you stand to lose proof that each update you receive came from the > hub. It's optional because you might not be worried about getting a > signature on each update. The callback URL is usually not publicly known, so > commonly just knowing it is proof enough. > > > > > Many thanks in advance. > > > Alok > > -- > Jeff Lindsayhttp://webhooks.org-- Make the web more > programmablehttp://shdh.org-- A party for hackers and > thinkershttp://tigdb.com-- Discover indie gameshttp://progrium.com-- More > interesting things
