Hey Waleed, This is why there's automatic subscription refreshing:
http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html#autorefresh Just wait for the Hub to send you the refresh request and if you don't know anything about the feed return a 404. In the meantime, ignore all the updates for callback URLs you don't know. This is why it's important to encode some information about the subscription in your callback URL (like a primary key in your database that points to the subscription record). Hope that helps, -Brett On Sun, Feb 21, 2010 at 4:20 PM, Waleed Abdulla <[email protected]> wrote: > Hi everyone, > I'm getting PSHB updates for feeds that I have previously subscribed to > but I don't want them anymore. To issue an unsubscribe request, I need to > know the hub url and the topic url, of which I only have the hub url because > I had encoded it in the callback URL when I subscribed, but I don't have the > topic URL (long story, don't ask :) > I started to parse the feed content to extract the topic URL from it > from the <link rel='self'> tag. That worked for a few feeds, but I quickly > found out that Blogger.com blogs actually put a different feed URL in the > "self" link, and they put the actual feed URL in a different tag: > <link rel='http://schemas.google.com/g/2005#feed' ...> > So I put an exception for blogger.com blogs to grab the topic URL from > the other link. That worked for many feeds, but I still have many other > updates I receive in which the feed doesn't contain a self link at all or > it's a bozo feed that can't be parsed. Am I missing something obvious? Any > suggestions? > Regards, > Waleed > >
