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.
That's true of the facade approach I described too - only plantSet knows about the caching... I still think you're adding unnecessary complexity...
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.
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).
