Closed GoogleCodeExporter closed 9 years ago
To update your callback URLs, why not just unsubscribe and resubscribe for all
existing subscriptions? How is this different? At first glance, the ability to
do a
bulk move of a whole set of subscriptions seems like a very complex idea to get
across, something that may unnecessarily increase the scope of the spec.
Original comment by bslatkin
on 27 Aug 2009 at 3:24
It does seem more of a convenience feature than a necessity that MUST be in the
protocol. Though, I can see a place for it in the protocol - a general update
mechanism
for subscriptions (renew subscriptions, change callbacks, and perhaps something
else in
the future).
Btw (and probably stating the obvious) - it's better to subscribe with the new
callback
first, then unsubscribe the older one so that no events are lost in between.
Original comment by izuzak
on 28 Aug 2009 at 11:47
After not hearing any more requests for this, I'm going to close it. We want to
keep the
protocol as lean as possible.
Original comment by bslatkin
on 8 Feb 2010 at 10:04
Original issue reported on code.google.com by
kugutsu...@gmail.com
on 20 Aug 2009 at 10:46