Strangely enough ;o) yes, I am happy to extend my CFCs. Long story short - I've got some data in a database that needs to be pushed up to the global internet site - so I'm building a series of CFCs that provide this Service...
So I've built a AbstarctBaseService that implements a basic 'init' method to store all the relevent database details, and also provides the neccessary methods to grab those details when querying said database. So all children init() methods call on that. I also wanted a mechanism, in which, I could easily implement a custom cachsing control across my series of 'Service' CFC's, at a later date, and this is the easiest way of doing it. Obviously I could create another CFC just to handle the caching capabilities, but I don't have the time (nor the inclination to do so). (That being said, I seem to have the time to gabble on on here ;o) ) Obviously, making the 'AbstractBaseService' not constructable was more from a purist point of view - I'm not actually going to instantiate it anywhere - but I would have liked to have put in the controls. So there you go - that's what I'm trying to do ;o) (Seems like design and patterns are all the rage atm - is good stuff). Mark On Tue, 27 Jul 2004 15:44:38 +1000, Barry Beattie <[EMAIL PROTECTED]> wrote: > Mark, just a quick Q: > > are you really sure you want to extend CFC's? inheritance has some > really good uses but can be easily over-used and tie the framework in > knots (extend->extend->extend...etc). just because you can doesn't mean > you should, although (of course) it's perfect for some designs > > Is there a particular design pattern you want to follow? or problem to > solve? > > just a thought > cheers > barry.b > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
