It's really not recommended to reuse callback URIs. The way I'm doing it here is just having the callback be unique per feed ID, with the ID encoded within the callback URI. If using PuSH 0.3 this is made even simpler by being able to pass along arbitrary query string data within the callback that Hubs must maintain unchanged, so besides some complicated encoding scheme (used pre-0.2), you can just URL encode the feed ID and pass it around as its own parameter.
Paddy Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Waleed Abdulla <[email protected]> To: [email protected] Sent: Wed, March 17, 2010 12:35:32 AM Subject: Re: [pubsubhubbub] Verifying the true source of an entry In non-aggregated content delivery, there's actually nothing > presented by the hub which can fully identify the feed. (This has > been something that always bothered me about using the same callback > for multiple feeds.) > + 1. There might be a reason for not sending feed and hub identifying information with the update but it's not clear to me. I hope this changes in a future update. Since every subscriber has to do that anyway, we might as well standardize it in the specs. Waleed NetworkedBlogs
