Open Stack

Excerpts from Clay Gerrard's message of 2014-09-29 16:05:14 -0700:
> On Mon, Sep 29, 2014 at 2:53 PM, Chmouel Boudjnah <chmouel at enovance.com>
> wrote:
> 
> >
> >
> > eventual consistency will only affect container listing  and I don't think
> > there is a need for container listing in that driver.
> >
> >
> well now hold on...
> 
> if you're doing an overwrite in the face of server failures you could still
> get a stale read if a server with an old copy comes back into the fray and
> you read before replication sorts it out, or read a old version of a key
> you deleted....

For tokens, there are really only two answers that matter:

* does ID==X exist?  * has ID==X been revoked?

I think as long as you have a separate container for revocations and
tokens, then resurrections would be fine. The records themselves would
be immutable so edits aren't a problem.

It would, however, be bad to get a 404 for something that is otherwise
present.. as that will result in an erroneous failure for the client.