RE: [CFCDev] Better way than dao, gateway, bean:

[John Farrar]

Excellent article on the importance of interfacing. (So the focus of the article… inherit vs. composition is interfacing stability) There is a good follow article mentioned…   http://www.javaworld.com/javaworld/jw-12-1998/jw-12-techniques.html   The other article isn’t a complete thought (not that the thought is ever complete… it just seems to be one concept running into another when you are approaching these topics to some people.) This concept is something that I have believed for a good while. The bigger issue is a consistent interface. It’s not data structure. You can store data in everything from Access (I don’t suggest proving you can do this.) to Cache (object relational data). If this is on a different layer it will still work. According to Cache they scale better than relational data. With all the talk about scaling it is very surprising there isn’t more chatter on this topic when it comes to data and object persistence. Anyhow, the subject of interface is what makes or breaks software. How you implement the objects that serve up the interfacing is expressed in the article as inheritance and composition. I like that article… and wish there were summaries such as these on cfcZone.org for review. It seems that would be simpler than banging the topics over and over… just point people to articles on the web site rather than banging out the concepts over and over in the discussion list.   I also believe that it isn’t evil to do inheritance and polymorphism. The point is the stability, life cycle, maintenance and control of implementation are more powerful using compositing. Yet there is more work required. The question by necessity includes the maintenance of code. If it’s a one up simple app… inheritance will likely cost less to build. On the other hand, if it’s a growing and changing application then compositing will likely cost less to maintain. (The issues of time and money are the key since time is the primary issue here that drives the cost up. It depends if this is a long range development situation or a short range situation.)   John Farrar   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Hardy Sent: Friday, August 19, 2005 6:17 PM To: CFCDev@cfczone.org Subject: Re: [CFCDev] Better way than dao, gateway, bean: <cfquery>   Hi there,   From the description you gave it did sound very much like inheritance. And that's not a bad thing, inheritance is extremely useful. Unfortunately it has some drawbacks too. Barney has covered the ground  well but here is a link to an article that discusses Inheritence vs Composition in greater depth.   http://www.artima.com/designtechniques/compoinh.html   Cheers, Pete (aka lad4bear)       at www.mail-archive.com/cfcdev@cfczone.org ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org