Hello, Another cairngorm question. I've noticed that using other frameworks like rails, that it's common to make one model, view and controller per table in a database. Using cairngorm I've always made just one controller with alot of actions registered with it. Probably know as a fat controller. Is it a good idea to break the one controller down into serveral controllers? It seems like it would be more reuseable. I learned cairngorm from the flex store example (flex 1.5) and several others. But it seems like the examples always are very simple and have only one table in the db. Is there a best practice? Why would you do it one way or the other?
Thanks in advance, Chris -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
