On Fri, 2008-07-18 at 21:33 +0300, Sancar Saran wrote: > And one thing. > > > (1). It is very convenient to pre-process static information at compile > > time rather than on every request (specific properties, content chunks, > > content relocation, etc). Additionally, it can compile to static HTML, > > One of my sites using 3rd party as data source (via xml). > > Their data may change any time, so we have to parse template files in each > request. > > What is your suggestion ? I didn't say it had to be static. I said it can be either static or dynamic. it can house modules, render module data, render arbitrary data. Essentially you can make static what needs to be static and make dynamic what needs to be dynamic. But the template engine isn't like how smarty does things. My engine can produce a PHP file with appropriate PHP code to load modules and render data at run-time. The difference is, when this page is requested by the browser, the template engine is not part of the run-time process. Only the modules are that produce the dynamic data. Of course if you have no dynamic data, no modules need be loaded (such as for CSS). In fact the PHP engine need not be loaded either if it's a true static content file. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
