On Fri, Oct 16, 2009 at 3:22 PM, Jay Rossiter <[email protected]> wrote: > > This is undefined in the spec. How should a hub handle multiple > subscription requests to the same topic by a single endpoint with different > hub.secret values? (Since this is the only persistent option.) > > Should it be allowed, rejected or should the new request overwrite the > existing subscription? > > A properly configured subscriber shouldn't ever do this, but imagine a > situation where DB corruption causes the loss of subscription information and > they begin resubscribing to everything. The invalid subscription would be > picked up by subscription-refreshing, but until that time (which could be > days, or weeks later)... what's the desired behavior?
Great question. I'd argue that the tuple (topic, callback) is unique and will overwrite any existing subscription regardless of its verify_token or secret. This is how the reference hub is implemented. The spec should properly define this. I've filed this issue to track that: http://code.google.com/p/pubsubhubbub/issues/detail?id=92 Thanks! -Brett
