In my application I subscribe and unsubscribe to many feeds. I keep
track of this in a database on the app server side. Unfortunately (due
to some bugs of mine) some subscription details were dropped which
caused my database to be out of sync with the actual subscriptions
from the hub. The net effect of this is that I get a lot of pushed
notifications for feeds that I am actually not interested in.

Is there a "proper" response code I should return to the hub when it
contacts me with data for a subscription that I don't want?
Essentially, something that should cause the hub to drop the
subscription.

I can't unsubscribe in the "proper" manner, because there is no
information as to exactly which hub is sending the data. This is
something that seems like an omission in the spec as far as I can
tell. There is not enough information in a hub push message to
actually unsubscribe from the feed.

Reply via email to