ID: 28790
Comment by: nong11yjyygy at yahoo dot com
Reported By: jnoll at prim dot hu
Status: Assigned
Bug Type: Feature/Change Request
Operating System: Debian GNU/Linux (unstable)
PHP Version: 4.3.6
Assigned To: pollita
New Comment:
very good
http://www.11nong.com
Previous Comments:
------------------------------------------------------------------------
[2004-06-16 17:30:45] pollita@php.net
I'll cut ya in on a secret: The statcache is only one entry long.
------------------------------------------------------------------------
[2004-06-16 17:28:42] phpbugs at spam dot raszi dot hu
It would be better if the file modification functions invalidate not
the whole statcache, only the entry of the modified file.
------------------------------------------------------------------------
[2004-06-16 16:29:51] pollita@php.net
Ilia was perhaps a bit short winded in his response...
This was actually discussed within the context of a feature change as
well and was turned down on the basis that it would create unnecessary
slowdowns without significant gain.
You should be aware when you're making multiple stat family calls to
the same file and call clearstatcache() accordingly. If you're
uncertain, then just call it anyway.
However, that said it may be prudent to introduce an .ini option to
disable the cache altogether now that stat calls work on arbitrary
wrappers. Let's leave this option open for PHP 5.1 for now.
------------------------------------------------------------------------
[2004-06-16 16:10:36] jnoll at prim dot hu
Okay, let me change this to a feature request!
After fclose(), the stat cache for that file should be cleared. Also,
unlink and maybe copy should do this.
If a function is KNOWN to change file stat data, it should clear the
cache.
The problem is that even a file_exists() call caches the data
(including the file size!), and this is easy to overlook, when you have
a bigger system.
------------------------------------------------------------------------
[2004-06-15 19:03:34] iliaa@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
This is to be expected.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/28790
--
Edit this bug report at http://bugs.php.net/?id=28790&edit=1