We have the difference between idle time and time to live.
> -----Original Message-----
> From: Weaver, Scott [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 30, 2002 11:25 AM
> To: 'Turbine JCS Users List'
> Subject: RE: How do you retrieve a collection keys for a cache region
>
> Another concern is removing refreshable cached items that have fallen into
> dissuse. If a cached object has not been touched by a get in a specified
> period of time, the next expiry interval that object should be removed
> instead of being refreshed. I think the turbine cache did this.
>
>
> > > I think the classes should have to implement a
> > common interface,
> > > but the name of the implementation class should be called
> > by reflection.
> >
> > What is the advantage of calling with reflection versus
> > casting here? If
> > they implement the interface they must have the method. I must be
> > missing something.
> >
> It confused me a bit also. However, I'm pretty green when it comes to JCS
> and I don't use reflection/introspection all that often, so maybe that's
> why
> I missed the logic.
>
> Scott
>
>
> > -----Original Message-----
> > From: James Taylor [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, April 30, 2002 11:08 AM
> > To: Turbine JCS Users List
> > Subject: RE: How do you retrieve a collection keys for a cache region
> >
> >
> > On Tue, 2002-04-30 at 10:12, Aaron Smuts wrote:
> > > 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.
> >
> > As long as the objects don't hold references to connection pools and
> > such it might not be such a big deal. A refresh method could
> > just go to
> > the PersistenceManager singleton and say 'refresh this object'.
> >
> > > 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.
> >
> > What is the advantage of calling with reflection versus
> > casting here? If
> > they implement the interface they must have the method. I must be
> > missing something.
> >
> > >
> > > > -----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]>
> > > > >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
