I wish I had that kind of flexibility. For this project, people expect to be
able to modify the database directly and see the changes percolate up to the
app in a reasonable period of time.

FWIW, I've never seen this work. I've run the section of code in a test
harness (guaranteeing only 1 transaction) and objects seem to never age out
of the cache. 

-----Original Message-----
From: Gray Jones [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] Aging and the LRU/Dirty Check cache


I have seen it work sometimes.  But its not as consistent or as accurate as
you'd think.  I think it has to do with whether the object is referenced by
other objects/transactions or not.

I'm pushing for us to flesh out our 'super amin' app so that people don't
have to make changes directly to the database.

-----Original Message-----
From: Smith, Kevin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 11:13 AM
To: [EMAIL PROTECTED]
Subject: [castor-dev] Aging and the LRU/Dirty Check cache


All -

Has anyone seen an object actually age out of the cache and get refreshed
from the database? If I read the online documentation correctly, this should
happen at some point. In my case, I'm using a time-limited cache with a
limit of 10 sec. My understanding is that if I wait > 10 sec to do a query,
I should get an object whose contents represents that of the database and
not the cache (because the cache entry has been flushed). I'm not seeing
that at all.

I've tried using the cache flush hack I posted to the list a few days ago,
but I'm running into transaction management issues which are beyond my
knowledge of the Castor source.

Any ideas?

--Kevin

-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to