Closed GoogleCodeExporter closed 9 years ago
Why 409 ("Conflict") rather than 403 ("Forbidden")?
Original comment by tonygarnockjones
on 5 Aug 2009 at 12:05
Further questions that are related:
From Mark Smith:
> One thing I don't see in the spec is if a hub is required to persist
> subscriptions to some data store. I can easily see someone
> implementing an in-memory hub (I believe the Python Twisted
> implementation a while back is like this) that doesn't save
> subscriptions, and as a subscriber, we don't know that a hub has lost
> our state or not.
>
> Is this something you intend to codify in the spec, or is it up to
> particular hubs? (And in that case, what is the reference hub on
> GAE's policy? If I specify 30 days as my lease, can I depend on that
> actually working?)
From Jeff Lindsay:
> Anyway, I'm not entirely sure it's necessary for the spec, at least as a
> requirement. It definitely needs to be stated clear if they are not
> persistent in any implementation ... but this is an interesting issue. You
> can definitely say an implementation needs to honor subscription lease, but
> it can't honor it if it's not running... I think that's implied ... it's
> interesting because most specs are about interfaces, not the state behind
> them.
Original comment by bslatkin
on 3 Sep 2009 at 6:50
Due to the approaching shutdown of Google Code
(http://google-opensource.blogspot.ch/2015/03/farewell-to-google-code.html)
we're moving all public PubSubHubbub development to the pubsubhubbub
organization on Github:
https://github.com/pubsubhubbub
The protocol spec resides under https://github.com/pubsubhubbub/PubSubHubbub
while the various client libraries and example applications have separate
repositories.
Wiki content has been migrated to the PubSubHubbub project as well:
https://github.com/pubsubhubbub/PubSubHubbub/wiki
Please re-open your issue on GitHub if it's still relevant.
Original comment by the...@google.com
on 18 May 2015 at 7:25
Original issue reported on code.google.com by
bslatkin
on 20 Jul 2009 at 6:32