Re[2]: Is Cheetah thread safe?

Hello Mike,

Saturday, October 4, 2003, 11:34:56 PM, you wrote:

> Template instances are not thread safe. Each thread should
> instantiate its own template.

Maybe I should create a singleton class to solve it?

> Webware's servlet caching mechanism is considerably better adapted to
> Webware's use situation than #cache is.  I would cache servlets and
> forget about #cache.  If you do use the two together, you'd get a
> multiplication effect; that is, the cache variables would be refreshed
> only when *both* Webware's cache and Cheetah's #cache happen to be
> expired simultaneously.  I suppose there may be some specialized uses
> for this.

I do not understand. I was using permanent cache for Chetah (without
father refresh at all). I do not know how Webware cache works and how
to interpret its "CacheServletClasses" and "CacheServletInstances"
variables (from Application.config file)

Is it mean, #cache feature of Cheetah is *useless* when I am using
Webware??? I changed from Spyce to Webware because I thought I cannot
use #cache for sets of inherited templates. I do not know to reject
#cache, because I need to cache some sql queries. I cannot do it with
pure Webware cache mechanism. I expected Cheetah to help me.

You know, I have much bigger experience with PHP and it's Smarty
templates. Their works in clear and easy to understand way.

> You don't say what the particular errors are, what kind of servlets
> you have, how you are using #cache, or when the errors occur, so I
> can't speculate further.

I tried once again. I switched off #cache. And... I still get the same
errors (sic!) as before. I wrote abnout it more in post "What is going
with __CheetahTemp files???"

-- 
JZ ICQ:6712522



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf