On Fri, Jun 15, 2012 at 4:47 PM, Maxim Lacrima <[email protected]>wrote:

> Hi!
>
> This is really strange!
>
> In my experience it doesn't matter how you subscribe - synchronously or
> asynchronously. The verification request from the hub always comes very
> quickly (usually in a half a second).
>

The verification request does indeed happen almost instantaneously, but you
won't receive content updates unless someone else subscribes to the same
topic with hub.verify=sync.

In order to receive notifications from the hub regarding blogger feeds you
> need to subscribe to the link with rel="
> http://schemas.google.com/g/2005#feed"; . In my experience if I subscribe
> to the feed using 'self' links iyou never get notifications, but if I
> subscribe using 'http://schemas.google.com/g/2005#feed' I get almost
> instantaneous updates.
>
> @ED209, it seems that you solved your problem... But what link[@rel] do
> you use to create subscriptions? If it 'self' then it is really strange,
> because it doesn't work for me.
>

You should use feed URL as Topic. If you can wget the feed, it means you
can also subscribe to it.


>
> On 15 June 2012 17:20, Roman <[email protected]> wrote:
>
>> I figured out what's going on.
>>
>> The subscriptions in the hub have an asynchronous component even when you
>> are subscribing with hub.verify=sync. Until the asynchronous part finishes,
>> no updates on the topic will be distributed to the subscribers.
>>
>> There is a huge backlog of asynchronous processing right now and I
>> estimate that it would take two weeks to process it. I nuked the backlog
>> and see that the hub has resumed processing submissions.
>>
>> Things should work for you once you resubscribe (with hub.verify=sync).
>> Could you verify?
>>
>> Roman.
>>
>>
>> On Fri, Jun 15, 2012 at 2:54 PM, Roman <[email protected]> wrote:
>>
>>> I'll take a look.
>>>
>>> Roman.
>>>
>>>
>>> On Fri, Jun 15, 2012 at 2:51 PM, ED209 <[email protected]> wrote:
>>>
>>>> Thanks for the quick reply Roman, but we already are subscribing with
>>>> hub.verify=sync
>>>>
>>>> anything else we could try? Any way to debug?
>>>>
>>>
>>>
>>
>
>
> --
> with regards,
> Maxim
>

Reply via email to