On Tue, Jun 24, 2008 at 1:08 PM, Dan Vega <[EMAIL PROTECTED]> wrote: > I think Sean brings up a really great point here. In very data centric > applications (bunch of forms and reports) a light mvc pattern to help > seperate your model and view might be all you need. Maybe only certain > features will follow a pattern. Its your job to learn the patterns and as > Sean said always be mindful of them.
I may be somewhat naive in what type of apps people are building, but I would guess that a good majority of apps can really be described as data centric. Any e-commerce site is basically that. Any customer management app is basically data centric. Calendars & events - data. While I know blindly running with the 5-1 cfc is not a good way to learn OO, I have found that the DAO / Gateway works and does make app maintenance easier. Encapsulating the CRUD and other "aggregate" selects makes the queries much easier to reuse. As does having a service layer that provides an API to get to those queries. Yes, we shouldn't argue about if the DAO & Gateway should be one CFC or not; that is more of a personal preference. But I don't think we should dismiss the usefulness of this for these "data centric" apps, which seem to be quite common. -- Matt Williams "It's the question that drives us." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" 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/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
