--- Begin Message ---
Hiya,
 
It does exactly that.  The MRU store can be figured for max objects in the same way as 
our current MRU.  As far as differenciating what is stored in persistent as opposed to 
transient, that could be done through configuration of different store "regions."  I'm 
fairly confident that this could be done with no change to the current code - just 
specifying a different region param in the xconf.
 
It really is a beautifully flexibile caching system!
 
Cool,
 
Corin
 

        -----Original Message----- 
        From: Unico Hommes [mailto:[EMAIL PROTECTED] 
        Sent: Fri 5/03/2004 4:00 p.m. 
        To: [EMAIL PROTECTED] 
        Cc: 
        Subject: Re: Turning off default MRU store
        
        



        Corin Moss wrote:
        > Hi Guys,
        >
        > I might be getting ahead of myself a bit here, but I'm going to try and
        > turn off the default MRU store, in favour of the JCS based persistent
        > store.  I'd like to try some tests on performance without the default
        > MRU - has anyone else tried anything similar? I've simply set the core
        > store's role to point to the JCS store implementation.
        >
        
        I guess I already got ahead of you when I renamed JCSPersistentStore
        JCSStore just now :-) (And merged it with the AbstractJCSStore BTW). It
        seems to me that JCS is both and it could replace all three stores:
        DefaultStore, TransientStore and PersistentStore.
        
        > The rationale behind this is that JCS implements a MRU store all on its
        > own - this simplifies things a bit as far as I'm concerned
        >
        
        Does it back memory stores with persistent stores in the same way that
        DefaultStore is doing? That is, a memory store upfront and a background
        task moving out items into a more persistent region when memory runs low?
        
        Unico
        
        

<<winmail.dat>>


--- End Message ---
================================================================
CAUTION: This e-mail and any attachment(s) contains information
that is intended to be read only by the named recipient(s). It
may contain information that is confidential, proprietary or the
subject of legal privilege. This information is not to be used by
any other person and/or organisation. If you are not the intended
recipient, please advise us immediately and delete this e-mail
from your system. Do not use any information contained in it.

================================================================
For more information on the Television New Zealand Group, visit
us online at http://www.tvnz.co.nz
================================================================

Reply via email to