It'd be nice to require that, but I'm not sure it's feasible. It doesn't allow for various failures that could occur on the hub side. Logically, the subscriber should be responsible for making sure that it's subscriptions stay active, by resubscribing when its subscriptions expire - automatic refreshing is just an optimization to that. To be robust, a client really should manage its own subs explicitly, instead of relying on the hub. --Ravi
On Sat, Oct 17, 2009 at 9:25 AM, igrigorik <[email protected]> wrote: > > > In terms of intent and the spec, subscribers should assume that if > > they have not received a subscription auto-refresh by the end of the > > lease seconds that something is broken and they should go and > > resubscribe to the feed. > > I hear what you're saying, but ack.. if that's true then that's very > annoying. All of the sudden the client has to become a lot smarter in > order to keep his own counters and expiry logic. Ideally, I'd like to > change that language in the spec to MUST instead of should -- hub > _must_ notify the client on subscription expiry.
