> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Hal Helms
> Sent: Tuesday, January 24, 2006 1:33 AM
> To: [email protected]
> Subject: RE: [CFCDev] CFML and Typing (was Bean and CFC question)
> 
> I was thinking about the cfproperty thing. While I like the idea a lot,
> it's
> going to be fatal for mixins, at least as I've implemented them, where any
> object could be mixed into any other object. I think it's important that
> the
> object having code mixed into it not have to know about the mixin object.

I've not looked art the "mixins" idea yet (sounds neat tho') but you might
want to take a look at the stuff I pointed to the other day.

I found CFPROPERTY to have at least a few problems.  It doesn't allow for
access definition (you may want variables private or abstract but still have
them defined in documentation).  Using it as a meta data generator might
impair it's use as a web services descriptor (you might have private
properties that you want to define but that you don't want exposed to the
web service.

So I left CFPROPERTY to the web service domain and created a meta data
injector of my own.  Each CFC can (optionally, of course) define all its
properties.  These will be cached during the pseudo-constructor phase.

The system already easily handles inheritance.  It could easily be used to
build aggregate supersets of multiple components.

The only major change I'd like to make is applying the metadata directly to
the existing metadata structure (if possible and performant) - right now the
metadata cache is contained either in the application or the server scope.
I don't like that as much.

Jim Davis



----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] 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).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to