On Tue, Jun 24, 2008 at 2:26 PM, Matt Williams <[EMAIL PROTECTED]> wrote:
> > > 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. > > This is true, of course. Every application has to use or manipulate some form of data. But I think the idea (at least on my side) is that when I say a "data-centric application" I mean literally that. Apps with virtually no actual behavior. A contact management app with a master-detail view and a data entry form. A reporting tool that queries a database and dumps out tables or graphs. These kinds of thing are extremely common, and are essentially nothing but a direct pipeline between the browser and the database: form > query > html table. Now an e-commerce site, on the other hand, I would say is probably going to be much more complex. We're getting into business rules (What's on sale? What discount tiers do I give to various customers? How do I calculate shipping and tax rates? What algorithms determine what featured items are on the home page?) Depending on how robust and feature-rich the application is, these can all get very involved and complex. And the business rules will probably change constantly. So this is where an OO approach would probably provide much more benefit. I suppose I'd say that the more rules there are and the more parts of the application are subject to change or variation, the more sense OO makes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
