Re: [SMARTY] cache+dynamic site - i don't get it...

From: Date: Thu, 02 May 2002 06:40:01 +0000
Subject: Re: [SMARTY] cache+dynamic site - i don't get it...
References: 1 2 3  Groups: php.smarty.general 
Request: Send a blank email to php-smarty-general+get-3973@lists.php.net to get a copy of this message
By cached you mean the smarty templates being turned into straight PHP scripts based on the template -- right? And turning it on and off being that check that's performed to see if the most current version of the template has been turned into PHP? Since it's not Smarty, but rather PHP that's doing all the database accesses, I don't see how having Smarty "caching" turned on or off makes any difference here since it only affects Smarty templates being pushed into straight PHP... Am I misunderstanding what you mean by "cached"? I've heard the PHP forms of the Smarty templates referred to as both "compiled" and "cached" so it's confusing sometimes :-) ----- Original Message ----- From: "g.p.ciceri" <gp.ciceri@acm.org> To: <szkaroly@freemail.hu>; <smarty-general@lists.php.net> Sent: Wednesday, May 01, 2002 10:45 PM Subject: Re: [SMARTY] cache+dynamic site - i don't get it... > I split the page template in several (sub-)template, > control caching at the main program (before > displying the sub-template), and use the include_php() > trick into the specific sub-template (where the db calls go). > In this manner, I can avoid the is_cached control. > > HTH > /gp > > > > Monte Ohrt wrote: > > > That is what is_cached is for. you put is_cached around your db calls. > > If the page is cached, then don't execute the db calls. > > > > Monte > > > > k wrote: > > > [SNIP]

« previous php.smarty.general (#3973) next »