|
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? --
![]() Jay Rossiter | Software Engineer/System Administrator Pioneering RSS Advertising Solutions [email protected] | Phone: 503.896.6187 | Fax: 503.235.2216 Website: www.pheedo.com | RSS: www.pheedo.info/index.xml |
- [pubsubhubbub] Multiple subscriptions of the same topic to t... Jay Rossiter

