Hi Ravi, Sorry for the delay in responding.
2009/10/11 Ravi Pinjala <[email protected]>: > > I'm trying to test that my aggregator works with automatic subscription > refreshing properly, but after setting a really short (10 minutes) lease > interval, I don't get any kind of request from the hub to refresh the > subscription. Also, I'm still getting notifications, so it seems that > the lease lasts longer than what's returned in lease_seconds by the hub. > > So, my question is, how strictly is lease_seconds interpreted by the > hub? is it intended to mean that the subscription will end at that time, > or that it won't end until some unspecified point after that time? And > if it's the latter, how long should a client wait before giving up on > the automatic refreshing, and trying to resubscribe? Great questions. Right now the reference hub implementation only clears old leases once per day. I'm soon going to be changing this to be much more fine grained (probably every 60 seconds). That explains the behavior you are likely seeing. Practically, Hubs SHOULD make a best-effort attempt to clean up your subscription within the lease time-frame. They indicate the effective lease_seconds value in the subscriber verification request that they SHOULD honor, but it's not a "MUST" in the spec. 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. Is that in line with your expectations? Is there any way the spec could make this more clear? Thanks for all the feedback, -Brett
