TomH
Visitor
|
Re:PHP templating systems - 2006/05/30 10:19
Consider alternative caching strategies...
If your db content is changed as part of a backend process...then that's where to place the caching process...whenever db updates made then update cache. Public users then will always see uptodate content and those pages will all come from cached objects.
If users are viewing _and_ changing content then slug the cache logic into those part of their interactions that modif the dbase.
If you want content navigation specific caching then consider evaluating TonyButStrong template engine in tandem with ezSQL database handler class. TBS has excellent page caching control and combined with ezSQL's excellent query caching control they give you great flexibility in this area.
There are some examples of various caching strategies/tricks using TBS/ezSQL at http://tomhenry.us/tbs3/
|
Forums 
Wednesday, 07 January 2009
Home | Wiki | Search | Forums | Job Board | Newsletter | Latest News | Reservations | Classified Ads | Podcast Archive | MyAccount | 
