Re: Function caching...
| From: | Zeev Suraski | Date: | Tue, 12 Dec 2000 10:48:36 +0000 |
| Subject: | Re: Function caching... | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-40941@lists.php.net to get a copy of this message | ||
At 10:30 12/12/2000, Kristian Köhntopp wrote:
Zeev Suraski wrote: There are *very* good reasons why it shouldn't happen. It's *extremely* dangerous, and you have to have a very good idea of what you're doing (for instance, you mustn't cache any function that depends on SQL or any other external data source that may change). In many cases even these can be cached, if you take some simple precautions.I won't argue that. I know that in many cases (probably many more) you mustn't cache it, and the precautions you describe as simple will actually be driving forces that would mess your application/database up bigtime. It's just a matter of likelihood - a mechanism that is prone to errors isn't a mechanism that can't be used. It's just that it is, well, prone to errors. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/