That's half of it. The other half is the reverse: the environment shouldn't know anything about the object's internals. That way both environment and implementation can change, but as long as the interface doesn't there isn't a problem.
Yes, attribute protection (as you call it) is missing from CFCs, but that doesn't really relate to 'this' at all, since you can overwrite a method with a variable (or another method) dynamically at any time. Which can lead to some subtle bugs, and also some very interesting capabilities, such as runtime injection of method wrappers for various things (logging, security, etc.). cheers, barneyb On 8/29/05, John Farrar <[EMAIL PROTECTED]> wrote: > Barney, > > Wait, isn't encapsulation the concept that the bean doesn't know anything > about the outside world? Could you give me your definition... it seems to me > it would be breaking something else... or I was given the wrong definition > on that one. (And the bigger issue with this is CFC's don't have protection > of attributes, thus I suggest they are only dangerous if the attribute could > have a method by the same name. Isn't this also correct?) > > Thanks, > > John Farrar > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- 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). 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/[email protected]
