jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Smuts <asm...@yahoo.com>
Subject Re: JCS Setup Questions
Date Mon, 07 Mar 2005 06:13:56 GMT

> True, but part of the reason to use a cache is for
> speed.  It is
> expensive to always have to reload a collection of
> 600-1000
> rows, so it is a perfect candidate for caching, but
> that is not
> acceptable if it is at the cost of having invalid
> data.
> 

That depends.  Some data is ok stale.  Bank account
data isn't.  The description of a book or some other
item at an online store, like the one I work for, is
ok.

 

> > 
> > You write the plugin, send it to us, and I'll put
> it
> > in a plugin jar along with the struts plugin. 
> 
> I may do just that, though the code would be pretty
> much the
> same as it is in the JCS plugin in the Hibernate
> 2.1.x source
> tree.  I could convert it to a JCS package and send
> it.  I'll
> try to do this when I get a chance.
> 

Sounds good.  

> > 
> > You can definitely set different values for
> different
> > servers.
> 
> Does anyone know how?  As far as I understand it,
> server
> instances in a Weblogic cluster utilize a
> cluster-wide JNDI
> tree, so how could you configure a separate value
> for each node?
>  
> > Either way, I think the remote cache is a better
> > option.  It solves your configuration problems,
> since
> > all the local caches can have the same settings. 
> It
> > does require that you run a separate process, but
> it
> > is a better model overall. 
> 
> That may be, but I doubt the managers and admins at
> my company
> would allow another process or server to run besides
> for the web
> servers.
> 

Oh well.  

Aaron




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


Mime
View raw message