Hi guys,

I'm looking at the 0.3 version of the hub and it seems that the expiration 
feature is required for all subscriptions. However, the 0.3 spec draft 
seems to suggest that hubs may decide if subscriptions will expire or not? 
Basically, I'm looking to build a hub where subscriptions don't expire and 
don't need to be reconfirmed - is it simply a matter of removing the cron 
jobs for subscription reconfirmation/cleanup or will the latter also result 
in unsubscribed subscriptions not being cleaned up (not sure if those are 
deleted straight away, or when subscription_cleanup is called).

If there is no clean way to set this up, I'll hack around, was just 
wondering if I'm missing some easy switch somewhere or something.

Cheers,
Martin

Reply via email to