I like the new names. (There are old versions named the same way.) The IComposite cache was for things that needed to get into the internals of the composite cache.
The ICache was supposed to be for auxiliaries. The cache hub was supposed to look something like an auxiliary to access classes. Aaron > -----Original Message----- > From: James Taylor [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 23, 2002 9:54 AM > To: [EMAIL PROTECTED] > Subject: Cache and CompositeCache > > The cache accessed via a CacheAccess and managed by a CacheHub is always > a composite cache, however currently in many places these are > manipulated using the ICache interface. I propose that we have them > (specifically CacheHubs factory methods) deal with the composite cache > directly (currently this would mean dealing with ICompositeCache and > Cache). > > Also, did we ever come to a decision on the renaming of Cache and > CacheHub? > > I'm probably going to go ahead with: > > Cache -> CompositeCache > CacheHub -> CompositeCacheManager > > unless anyone has a better idea or and objection. I was also thinking we > might want to just get rid of the ICompositeCache interface since I > can't see any good reason for it. > > -- jt > > > > -- > To unsubscribe, e-mail: <mailto:turbine-jcs-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-jcs-dev- > [EMAIL PROTECTED]>
