coarse-grained or fine-grained?

[Dustin Sallings]

On Dec 13, 2007, at 8:43, marc2112 wrote:

> The last consideration I'm thinking through in all of this is how to  
> manage serializable class versioning.  Do ppl generally take an  
> optimistic approach here and if there is a serialization exception  
> on read, just replace what's in the cache?  Or do you include a  
> class version indicator as part of the key?  If it's part of the  
> key, how do you make sure that there aren't two live versions with  
> potentially different attribute values in the cache.


	The only thing you can really do here (and what I do), is to ignore  
values you can't deserialize.  i.e., consider them a cache miss.  If  
you have two incompatible classes caching in the same namespace, you  
really have an unworkable problem.  I'd recommend you not do that.  :)

-- 
Dustin Sallings