[pubsubhubbub] Re: automatic sub refreshing

[Jay Rossiter]

I'm against this.  I think that it's the subscriber's responsibility to know that it will expire.  Sections 6.1, 6.2.1 and 6.3 logically confuse each other in that "Hubs MAY choose to respect this value or not, depending on their own policies," and "Hubs MAY make the hub.lease_seconds equal to the period the subscriber passed in their subscription request but MAY change the value depending on the hub's policies," but "Before a subscription expires, Hubs MUST recheck with subscribers to see if a continued subscription is desired."     Your doctor may give you a courtesy call to remind you about your appointment, but it's your responsibility to know when it is even if they can't reach you or forget to call. 1.    You may request a 10 second lease.  The hub's policies may dictate that it doesn't accept leases less than 48 hours and modify the value returned in the subscription verification.  If the subscriber doesn't keep its own information... how does it know that the subscription is active in the first place, and how would they know it was expired?  2.    There will always be communication errors - if the hub can't communicate with the subscriber due to errors at either end, or in-between, the subscriber should still know that its subscription has ended.  If I attempt a verification and a subscriber's server error causes a 404 or 200-with-bad-challenge to be returned, I'm not going to continue trying to verify.  The subscriber is left "without verification" due to no fault of the hub.     I think that it's an absolute requirement for the subscriber to be able to handle their own data. On 10/17/2009 7:25 AM, igrigorik 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. -- Jay Rossiter | Software Engineer/System Administrator Pioneering RSS Advertising Solutions jrossi...@pheedo.com | Phone: 503.896.6187 | Fax: 503.235.2216 Website: www.pheedo.com | RSS: www.pheedo.info/index.xml