You have to think about how this refreshable object will behave when passed to another machine or serialized to disk. You don't want to serialize all your utilities.
It might be easier to add a listener by name to the element attributes. In the cache hub when an element is expired on request, or in the shrinking memory cache when an element is automatically expired, you'd have to call the class. I think the classes should have to implement a common interface, but the name of the implementation class should be called by reflection. > -----Original Message----- > From: Weaver, Scott [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 30, 2002 8:34 AM > To: 'Turbine JCS Users List' > Subject: RE: How do you retrieve a collection keys for a cache region > > Give me reference point to start at and I will. > > > Scott > > > > -----Original Message----- > > From: James Taylor [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, April 30, 2002 8:25 AM > > To: 'Turbine JCS Users List' > > Subject: RE: How do you retrieve a collection keys for a cache region > > > > > > > > > I have used this that in the past (pre-JCS) and was happy with the > > > technique. Any chance this type of functionality could > > find it's way into > > > JCS? > > > > Sure thing. Of course, the fastest way to see it is if you write it =] > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > >
