Hi Chris, thanks for the reply..I am checking on some of the previous discussion on this group..and hopefull will be able to find some answers..
regards, Ritesh On Mar 30, 3:50 pm, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > On 3/30/07, bingo <[EMAIL PROTECTED]> wrote: > > > > > looking forward for some ideas.. > > Regards > > bingo > > This is just my own experiences, but I hope it helps... > > When you have a web page that has a mix of static and cacheable > information, you will want to consider breaking the content down into > elements and determining which of those elements you can cache. You > can't cache everything, so figure out for each piece of data you > display how long do you think you can cache it for before the user > complains about it not responding. > > You will end up doing some extra code to handle caching, like keeping > user data cached until it has been changed by the user themselves or > until your cache limit has been reached. > > This isn't a CakePHP issue at all, it's a generally program > architecture and strategy issue. Google is your friend for finding > hints on how to do it. > > -- > Chris Hartjes > > My motto for 2007: "Just build it, damnit!" > > rallyhat.com - digital photo scavenger hunt > @TheBallpark -http://www.littlehart.net/attheballpark > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
