Here's roughly how the hub functions. - The hub stores the last version of each feed. - On publish request, the feed is downloaded. - The hub removes unchanged entries from the feed it just fetched. Any kind of change in the XML except for comments is considered a change. - If no entries remain in the feed, nothing else is done. - Otherwise, the entries are sent to all feed's subscribers.
On Fri, Aug 16, 2013 at 12:08 AM, Isosceles <[email protected]> wrote: > I'm curious what was the culprit in rusty's case? I think I'm > experiencing a similar problem. The subscriber is verified successfully. > According to pubsubhubbub.appspot.com - Last verification error: n/a. > Last delivery error: n/a. The very first time the content is published, > the entire feed gets posted to a subscriber. > That's expected because there is no previous version of the feed in the hub data store, so it treats all entries as new. > The callback URL gets called and a full feed is delivered. However, > both Subscriber and Publisher debuggers claim that the last item received > and last item delivered are a single (most recent) entry in the feed. > The debug page always shows a single item even if the last update contained several. > Anyways, when the feed is then updated with a newer entry and published, I > get a 204 response and the Publisher debugger updates "Last successful > fetch" and "Last ping" fields. > Are you sure the feed's content is actually changed before the publish request is issued to the hub? Roman. -- --- You received this message because you are subscribed to the Google Groups "Pubsubhubbub" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
