Joseph Scott wrote: > The first obvious reason for stopping is to send the hub an > unsubscribe request. The second reason I'd say (as has been talked > about on another thread on this list) is for the subscriber's callback > URL to start returning an error status. From the point of view of the > hub I'd consider anything that is >= 300 an error and reason to > suspend the callback URL.
I noticed that in the PuSHPress code, and I think that's a very sensible move. I hope other hubs will follow your lead. However, it's worth noting that spec disagrees. From section 7.3: "Hubs SHOULD retry notifications repeatedly until successful". Where successful is defined as "an HTTP success (2xx) code". If a client is not coping for some reason, perhaps returning 503s or not even able to respond at all, the recommended course of action is to flood their callback with even more data.
