jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From WYo...@metasolv.com
Subject RE: Configuration Attributes
Date Thu, 29 Jan 2004 15:15:19 GMT
The javadoc does provide some help on attributes.
http://jakarta.apache.org/turbine/jcs/apidocs/index.html

Try the javadoc for ICompositeCacheAttributes and look at the index.

WY


-----Original Message-----
From: Estefano Eduardo [mailto:eduardo.estefano@siemens.com]
Sent: Thursday, January 29, 2004 3:04 AM
To: Turbine JCS Users List; karl.baum@tallan.com
Subject: RE: Configuration Attributes


I think that will be very helpful for everyone. The documentation is
really lacking.

-----Original Message-----
From: Karl Baum [mailto:kbaum@tallan.com] 
Sent: Thursday, 29 January, 2004 0:18
To: 'Turbine JCS Users List'
Subject: RE: Configuration Attributes


Unfortunately I don't know if any such doc off the top of my head.  If I
get some time maybe I'll put one together.. unless of course someone on
this list knows of some existing documentation.

-----Original Message-----
From: bobby buche` [mailto:bs_scout@hotmail.com] 
Sent: Wednesday, January 28, 2004 5:53 PM
To: Turbine JCS Users List
Subject: Re: Configuration Attributes

Thanks for the helpful information it really clarifies that for me.
While on the subject is there some documentation that might describe all
the available attributes.


----- Original Message ----- 
From: "Karl Baum" <kbaum@tallan.com>
To: "'Turbine JCS Users List'" <turbine-jcs-user@jakarta.apache.org>
Sent: Wednesday, January 28, 2004 4:44 PM
Subject: RE: Configuration Attributes


> If you want to control the life of an object in the cache, use 
> MaxLifeSeconds.  In this scenario, no matter how popular an element is

> in the cache, it will become stale when the MaxLifeSeconds is reached.
>
> If you want to control how long an object can remain idle before 
> becoming invalid, use MaxMemoryIdleTimes.  In this scenario, as long
as
> an element is accessed frequently, it will not become stale.
>
> ShrinkIntervalSeconds controls how often the MemoryShrinkerThread
runs.
> This thread looks through the cache for stale elements.  If it finds a

> stale element, it removes it from the cache.  If you do not have this 
> thread enabled, JCS will not know an element is stale until the next 
> time it is accessed.
>
> -----Original Message-----
> From: bobby buche` [mailto:bs_scout@hotmail.com]
> Sent: Wednesday, January 28, 2004 2:44 PM
> To: Turbine JCS Users List
> Subject: Configuration Attributes
>
> I'm need to set up different cache regions with different timeouts of 
> the objects within the different regions.  For example  Region A the 
> life of the objects are 24 hrs.  Region B the life of the objects 60
> minutes and etc.   Do I want to use MaxLifeSeconds in each region to
do
> this.  Is there anywhere I can get a good descriptions of all the 
> attributes that the configuration can be set to.
>
> What is ShrinkerIntervalSecond and MaxMemoryIdleTimeSeconds.
>
>
> Brian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
turbine-jcs-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
turbine-jcs-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message