I also thought about using a status code at first, but then I thought it's probably more consistent if we return plain text "unsubscribe" because that's how the hub expects subscription verifications to respond. But either approach works.
Anyway, I thought I'd share the idea with the list here. Now I'm off to go implement the explicit un-subscribe requests (admittedly, I left them as the last thing on the todo list ;) On Mon, Feb 15, 2010 at 4:36 PM, Jeff Lindsay <[email protected]> wrote: > I agree it's *not that hard* to make a request to unsubscribe. However, > maybe it's worth a special status code response to mean "unsubscribe now!" > ... a convenience method for unsubscribe. > > Then again, you'd think if the subscriber endpoint knew enough that it > could return a status code or "unsubscribe" (don't like that approach at > all), it could also just make the unsubscribe request in the update callback > request. I don't know. This sounds like trading a one-liner for a one-liner. > And an unsubscribe status code is more elegant, but becomes a special case. > > On Mon, Feb 15, 2010 at 4:15 PM, Josh Fraser <[email protected]> wrote: > >> I'm confused. It seems to me the unsubscribe request is simple enough >> already that you could just fire off unsubscribe requests whenever it >> makes the most sense for you. Adding the ability to respond with the >> word unsubscribe wouldn't cut down on the number of requests since the >> hub would still need to verify the unsubscribe. Of course, the hub >> could send a special unsubscribe token with each notification, but >> that would probably add up to more wasted bytes than the occasional >> unsubscribe. >> >> >> On Feb 15, 4:57 pm, Waleed Abdulla <[email protected]> wrote: >> > Hey everyone, >> > While implementing PubSubHubbub and using it in production, I >> realized >> > that there are several situations in which I need to un-subscribe from a >> > feed. Per the specs, the right approach, is to send an unsubscribe >> request. >> > While this works, there could be an easier way: What if, as a >> subscriber, >> > when I receive a ping for a feed that I don't care about anymore, I >> simply >> > reply with the word "unsubscribe" in the body to tell the hub to get me >> off >> > the list? >> > >> > When I receive a ping, I have to check it out and decide what to do >> with >> > it, and that's the perfect time to decide if I want to unsubscribe. By >> > making it super easy to unsubscribe, I believe we'll have less pings >> that >> > get ignored because the subscriber can't be bothered to send a proper >> > unsubscribe request. Thoughts? >> > >> > Regards, >> > Waleed >> > > > > -- > Jeff Lindsay > http://progrium.com >
