I need an access point to all auxiliary caches to display their configurations in an admin tool. I was thinking the access point to Auxiliary Caches was the AuxiliaryCacheManager implementation classes, similarly to how the CompositeCacheManager can access all CompositeCache's. However, I noticed the AuxiliaryCacheManager classes take a CacheAttributes argument in the singleton getInstance method. Does that mean the CacheManager returned only has access to the AuxiliaryCache's configured with those CacheAttributes? Any help would be greatly appreciated. Thanks.
Karl ----- Original Message ----- From: "James Taylor" <[EMAIL PROTECTED]> To: "Turbine JCS Developers List" <[EMAIL PROTECTED]> Cc: "Baum, Karl" <[EMAIL PROTECTED]> Sent: Saturday, April 12, 2003 12:35 PM Subject: Re: FW: cache.ccf - db > > I definitely like this idea. > > Off the top of my head, the best way I see to do this is to make the CCM > entirely bean / property configurable and then make the different > configurators more like factories. Have one implementation to build a CCM > from a property file, another from a database, another from an Avalon > Configuration instance... > > The only trick here is that the properties are saved and used directly when > creating auxiliaries. We will need to store that information in some > intermediate form (which is a good idea anyway). > > How does that sound? > > "Baum, Karl" <[EMAIL PROTECTED]> writes: > > > What we are looking to do is configure the caches from the database > > instead of the cache.ccf file. Obviously overall we are using JCS in an > > attempt to reduce costly hits to our back end databases. > > > > I was thinking the CacheConfigurator should be an interface and the > > default implementation would be the CompositeCacheConfigurator. A > > different cache configuration implementation may be optionally supplied > > at runtime. So for example, we could easily load our configurations > > from a database. > > > > Let me know what you think? Thanks. > > > > Karl > > > > -----Original Message----- > > From: Aaron Smuts [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 09, 2003 6:49 AM > > To: 'Turbine JCS Users List' > > Subject: RE: cache.ccf - db > > > > The point of the disk cache is to keep the data close and available. > > > > I did start implementing a db disk cache, but it was too slow. > > > > The cache allows any object. The disk cache can take any serializable > > object. What kind of field can you use in a database. A BLOB? That's > > just too slow. > > > > Aaron > > > >> -----Original Message----- > >> From: Ungcharoen, Kevin [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, April 09, 2003 10:39 AM > >> To: '[EMAIL PROTECTED]' > >> Subject: cache.ccf - db > >> > >> > >> Has anyone implemented a way to read/load those name-value cache > >> properties > >> from a database, instead of reading from the file (cache.ccf) ? We are > >> encoutering a situation where having to configure and maintain the > >> cache.ccf > >> file in so many servers (20+) might not be the best way to approach. > >> > >> Thanks, > >> Kevin > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: > > [EMAIL PROTECTED] > >> For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
