I think it's a pretty solid way to do it. I'm running a dashboard using the same type of code. I don't know how to use the cache to limit queries to the database, but if you're considering building a dashboard for your application, it kind of suggests that the data is going to be changing so quickly that the dashboard is always presenting "something new." If that's the case, you'd be putting potentially more burden on your server by having it cache data as well as query for it intelligently.
I wouldn't worry about it unless you run into problems. Your code looks pretty solid to me. On Feb 24, 1:10 pm, floydbrush <[email protected]> wrote: > First of all, excuse my poor english. > > Well, I need to develop a homepage for my job. They want a dynamic > homepage similar to Wordpress. A homepage formed by differents parts > like a dashboard, showing specific information about the whole > website, and ordering/showing these parts in different ways. In > addition, they could add new parts in the homepage at future easily. > > I thought a lot about the best way to do it, and I've based it on this > posthttp://teknoid.wordpress.com/2008/12/16/how-to-build-a-dashboard-for-... > of teknoid blog. > > > I have some doubts about it: > > - Is it really the best way to do it? > - Can I use cache in models to limit the requests to the DB? I know > about cache in elements but I'll only use elements to show the data > passed from the dashboard controller. > - Is there any other solution better than I'm using at getData() > function to call a subclasse function? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
