Cool stuff. In CachedObject and RefreshableCachedObject, the simple public
methods probably need to be synchronized, multiple threads could be
simultaneously accessing and changing some of the fields in these objects.
Also, in TurbineGlobalCacheService.clearCache(), the operations of removing
or refreshing the objects should be sync'd. I'll take a stab at a patch in
the morning if there are no objections (or I'm blatantly wrong).
Chris
[EMAIL PROTECTED]
----- Original Message -----
From: "Nissim" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 03, 2000 12:56 PM
Subject: cache: new features and threading issues
> Hi all,
>
> I just added a new feature to the RefreshableCachedObject. Now you can
> set a TimeToLive value in there, and if the object doesn't get touched
> in the cache for that time, then it will be removed. If you set the TTL
> to a negative value (the default) then it will stay in the cache
> indefinitely, refreshing itself whenever it expires.
>
> There are still threading issues in the cache as discussed previously in
> this list. Can someone with more experience with that stuff take a look
> at TurbineGlobalCacheService.java please.
>
> Thanks
>
> -Nissim
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
