hi Brett, the topic before has already anwsered my question
I always figured this could be solved by using a unique callback URL per hub rather than per feed. The hub is going to know the callbacks for all the feeds on its server anyway - you only need to protect the callbacks associated with other hubs. Or is there some reason why that wouldn't work? Regards James
I think this is a good way how the hub can identify to the consumer. I.e. as callback you post to the hub your callback with an GET variable "hash" with some random values and if the hub post new content you can identify them by this hash and according to the spec "6.1.1. Subscription Parameter Details" GET parameters are allowed in the callback.
regards
