Re: [SMARTY-DEV] On caching mechanics
| From: | Konstantin | Date: | Wed, 03 Sep 2003 07:10:19 +0000 |
| Subject: | Re: [SMARTY-DEV] On caching mechanics | ||
| References: | 1 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-1847@lists.php.net to get a copy of this message | ||
> > Imagine that first process creates directory for cache
> > file, at this moment second process makes a sort of
> > clear_all_cache(), which removes directory structure,
> > and then first process cannot open file for writing.
I don't know. I know there was a theoretical problem with
locking files, and that is why temporary files used in
smarty_core_write_file(). Removed directories is another
problem.
> It seems to me that its more of a
> logging issue than an actual problem. Perhaps @ will
> help?
Well, problem writing cache file is really not a problem,
cache will be regenerated on next request (but on a not
properly set up project this may be permanent problem, so
at development time warning may be useful). The same
function is used in smarty_core_write_compiled_resource(),
and problem writing it is really a problem for this
display() request. But this is more rare, since compiled
templates dir never gets cleared in normal work flow.
> > Warning: Smarty error: problem writing temporary file
I suppose to change this error level to E_USER_NOTICE.
Konstantin A. Pelepelin