Andrew, I'm curious. Given that you say this:
> > I don't need to do encapsulation here, and again this one of >many examples >in our framework were I don't need to worry about it... My >choice not yours, >don't force anything onto me. Like I said I understand the >risks and the >dangers and it is all taking into consideration when I design >my component. > Specifically the bit where you say "Like I said I understand the risks and the dangers" What exactly was it about this statement that you found so laughable? "Although putting data in the this scope is perfectly valid and will not cause any errors, it generally isn't seen as a good idea. The main reason being that you lose the ability to tightly control that data from within the CFC, so breaking the encapsulation. That leads to increased overhead when you try to maintain the code, because you can't just look at what's happening inside the CFC before making changes. You have to also look at where it is used and how it is used to make sure none of the data in the this scope is being added, modified or removed by external code." Regards Spike -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org --- 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/
