Stupid question... If you are going to build an object that wraps application variables... why not just store the variables inside the Object itself, and just make it a singleton in the application scope and/or pass it to all your other objects at startup?
Or am I missing something obvious? Mark On 28/10/05, Nathan Strutz <[EMAIL PROTECTED]> wrote: > > So it seems to me that I could, without hurting encapsulation badly, > create a cfc called application.static, which has getters for > application variables as an encapsulation hack, and call <cfif > application.static.getMode()>...</cfif>. The static keyword is in > there to make it obvious what I'm doing. > > Well, i've kind of rambled on. I know you've all got thoughts and > opinions, so have at it. It's just an idea i was kicking around. > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 ---------------------------------------------------------- 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]
