On Friday, August 15, 2003 6:18 PM, Sean Corfield wrote:
> I also think that inheriting from a cache object is poor OO design
> since your "plantSet" does not follow the "is-a" relationship to the
> cache object. If plantSet needs caching machinery, it should use an
> instance of the cache object - composition, not inheritance.
But my plantSet object "is-a" cached object! Isn't it?
If I change plantSet to use an instance of the cached object, am I then
doing what you typically suggest?
> On Friday, Aug 15, 2003, at 15:56 US/Pacific, Brad Howerter wrote:
> > I think this is pretty cool, because now I don't have to be aware of
> > wether
> > or not plantSet is cached from anywhere outside of plantset, I can
> > just call
> > createObject("component", 'plantSet') and get the cached version.
> I still think you're adding unnecessary complexity...
If you think that's true, you obviously haven't seen what I had before.
:-) Seriously, if I am, then I don't fully understand what you are
suggesting is the better way to handle the data.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev'
in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
