Julian,
I'm not referring to the protocol. It's the nature of any distributed
system that it suffers from unreliability due to the wide range of moving
parts. When you deal with a lot of feeds, those failures start to add up to
the point that you have to build a back up plan for them.
Waleed
On Mon, Sep 12, 2011 at 1:13 PM, Julien Genestoux <
[email protected]> wrote:
> Waleed,
>
> I am not sure why you have issues, but I think it's wrong to say
> pubsubhubbub is unreliable. there may be issues, but they are only due to
> implementation issues... not to the protocol. It is hard to debug, but it
> can be done, and I believe this community has been helpful and have been
> able to fix issues often times.
>
> Pankaj, I have offered help many times...
>
> Julien
>
>
> On Mon, Sep 12, 2011 at 8:42 PM, Waleed Abdulla <[email protected]> wrote:
>
>> I don't know if you're having trouble with all the feeds you're working
>> with, or with a small subset! But here is my own personal experience with
>> PSHB in case it helps:
>>
>> I subscribe to a lot of feeds and I've learned that, in general,
>> PubSubHubbub is not a reliable system. It's a distributed system that
>> involves the publisher, hub, and subscriber communicating over the Internet,
>> which means that any bug or issue at any point in the chain will cause a
>> notification to be lost. Often the issue is when a publisher doesn't send a
>> notification to the hub, and sometimes the hub is to blame, and so on.
>>
>> The way I handle it is that I have a slow polling process that fetches
>> feeds once a day. If my polling process fetches a post that's not in my
>> database, then I know something is wrong because that post should have been
>> received already through a PSHB notification. So I mark that hub is
>> "potentially broken", and put that feed on a faster polling process for a
>> month (in the hope that the hub gets fixed in that time), and then repeat
>> the process.
>>
>> Waleed
>>
>>
>>
>>
>> On Mon, Sep 12, 2011 at 2:49 AM, Pankaj Jain <[email protected]> wrote:
>>
>>> Hi Julien,
>>> When you say "this feed uses the pheedo hub" you're referring to the
>>> nytimes feed, right? That still wouldn't explain the Google Reader feed
>>> problem. I can also give you 10-15 other feeds that I'm not receiving any
>>> notifications from the appspot hub.
>>>
>>> I'm going to make a few changes to test with some other hubs but no code
>>> has changed on my side, I just stopped receiving notifications unless I
>>> manually go and publish the feed(s).
>>>
>>> Thanks!
>>> Pankaj
>>>
>>> On Sep 12, 2011, at 2:49 PM, Julien Genestoux wrote:
>>>
>>> Pankaj,
>>> this feed uses the pheedo hub. You want to see with pheedo if they have
>>> anything wrong with their hub... or again, if you're not doing a mistake
>>> yourself, by testing your code with another feed on another hub.
>>> Julien
>>>
>>>
>>> On Mon, Sep 12, 2011 at 11:11 AM, Pankaj Jain <[email protected]>wrote:
>>>
>>>> Ok, I'm not entirely nuts. The problem is persisting not just for my app
>>>> but also within friendfeed. Take for example, this Google Reader topic:
>>>>
>>>>
>>>> http://www.google.com/reader/public/atom/user/18179744707000356486/state/com.google/broadcast
>>>>
>>>> I share items from Google Reader and no notifications hit my FriendFeed
>>>> account or my app. However, when I go and publish the feed manually, both
>>>> FriendFeed and my app receive notifications.
>>>>
>>>> The reason I think it's more than Google Reader is because I'm not
>>>> receiving notifications for other topics either, e.g.
>>>> http://www.nytimes.com/services/xml/rss/nyt/start-ups.xml
>>>>
>>>> Any suggestions would be welcome.
>>>> Thanks!
>>>> Pankaj
>>>>
>>>
>>>
>>>
>>
>
