It's not a big deal for hobo, since the controllers are very lightweight and many dryml calls can be like mini controllers into themselves. But for rails code, it helps to keep things less coupled if you can have your db stuff solely in the controller. It also helps to be able to see how much time is from the DB and how much from the rendering if you're doing optimization.
On Dec 6, 2:13 am, Tom Locke <[EMAIL PROTECTED]> wrote: > > The other possibility I can think of would be useful in production > > mode, adapting initial loads for a particular controller/action based > > off what gets loaded after the controller. DRYML tends to blur the > > line between view and controller and sometimes it makes it quite > > difficult to keep it from making extra DB calls in the view. > > Personally I don't see what the fuss is about not making DB calls > during template rendering. Absolutely right though that we make more > DB calls than we should at the moment, and need to find ways to reduce > these. > > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
