Sure. Your provider could do whatever you wanted in terms of using XYZ for data caches, ABC for query caches, and DEF for general caches...
Another one is an optimistic tree-cache for entity data caches, and a pessimistic tree-cache for the others. Etc... -----Original Message----- From: Max Andersen Sent: Thursday, June 01, 2006 7:06 AM To: Steve Ebersole; Hibernate development Subject: Re: [Hibernate] CacheProviders > Additionally, we may want to split the Cache interface into separate > interfaces also based on usage; this would only be intended to allow > clearer definition of the capabilities allowed from each usage scenario. sounds like a good thing, code-readability/maintainability wise. > > Another nice benefit of this would be to allow "mixed providers". Like > imagine a clustered data cache along with a local query cache. +1. What about "mixed providers" in general ? e.g. being able to use EhCache for some entities and JBossCache for others ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
