Storage API changes

[Marvin S. Addison]

> A version of the storage API with some of the annotation work you did
> is checked in now. I left one bit out, I think it creates more
> complexity than I'm comfortable with to put the versioning support
> into the objects directly because of how the API works, but most
> subsystems won't need the versioning support anyway.

I've reviewed and looks good. Since I don't fully understand the use 
cases for versioning, I trust your reasoning for dropping @Version. I 
would like to point out, though, that there is nice symmetry between 
that annotation and the JPA annotation that serves a similar purpose, 
which was my rationale for including it. (Though due to my unfamiliarity 
with use cases, I didn't have a clear picture of how to use it, so 
dropping is probably best.)

I think the annotated object support will provide a very usable object 
persistence facility for objects that naturally have 
key/value/expiration semantics; CAS tickets fall squarely in that use 
case so I'm happy.

M