I agree that smarty is a great drop in view replacement for cake and it is what I use. However, for user specific differences, my best bang for the buck has been long term model caching. I use Pear's Cache_Lite in my model classes where I know a lengthy operation can be cached. I create accessor method in the model which performs the query(ies) and caches the results for several hours. If you categorize your caches correctly, then you can invalidate only the ones affected by a data change. The advantages I get are some caches are 5 minutes, some are 15 hours - I decide how long based on the data stored. Many times what I store is not table data but end result of large calculations specific to my needs. Pages that would take 5+ seconds to load everytime now take 3 seconds on the first hit and <1 for subsequent hits by the same user (Iknow it doesn't add up, it reuses other caches). Also the advantage is storing the caches on the local file system. That way multiple webservers have local caches and do not hit the network or database to get a result - except when the cache is stale.
HTH, David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
