Is the general logic to slice the page into some general pieces. For example
ones that have always general data and those that change. Then the ones that
don't change are streamed to the user using passthrough and the rest of the
page is generated dynamically with the newest relevant data.
The most efficient way would be to cache the heaviest parts of the
scripts. Such parts are database connections and its queries, templates
rendering and any other things like XML, large data loops etc..
What I would suggest is to modulate your application logic by sections
of different
Smarty template will allow you to cache certain
pieces.
http://smarty.php.net
olinux
--- Krzysztof Dziekiewicz [EMAIL PROTECTED] wrote:
Is the general logic to slice the page into some
general pieces. For example
ones that have always general data and those that
change. Then the ones
Though, I would not reccomend it to you as your caching mechanism. Only
for when you are actually using Smarty.. which is still makes no much
sence since Smarty is saving the compiled version of your file.
Maxim Maletsky
[EMAIL PROTECTED]
www.PHPBeginner.com // where PHP Begins
On Mon, 14
4 matches
Mail list logo
