Caching Patterns in ASP.NET

Question

So I just fixed a bug in a framework I\'m developing. The pseudo-pseudocode looks like this:

myoldObject = new MyObject { someValue = \"old value\" };
cache.Inse         


        

Answer 1

I've done similar things, but I got around it by cloning too. The difference is that I had the cache do the cloning. When you put an object into the cache, the cache will clone the object first and store the cloned version (so you can mutate the original object without poisoning the cache). When you get an object from the cache, the cache returns a clone of the object instead of the stored object (again so that the caller can mutate the object without effecting the cached/canonical object).

I think that this is perfectly acceptable as long as the data you're storing/duping is small.