On Jul 28, 2011, at 9:58 AM, Christian Grobmeier wrote: > I mean - transparent migration, transparent API, and just in case > there is something going on I get a warning. Sounds like a good deal > to me.
Yeah, I am leaning to #3 with a warning which has no performance tradeoffs and still lets the user know that he may be doing something wrong. > Spoken with my user hat on, I never used EHCache or OSCache directly To me there's an important scenario when XyzCache is used by the application outside Cayenne for its own caching needs and then Cayenne integrates into the same instance of cache provider to do its own thing. This way when setting cache group expiration policy, or invalidating a cache group, I can control both Cayenne and application cache entries in one place. Although even OSCache provider didn't handle this scenario out of the box (it would create its own cache instead of integrating with an application one, so I'd write my own provider). I guess with EHCache we can think how to handle this scenario. After all now we have DI that would allow users to pass their own CacheManager to the provider. Andrus
