I personally use application variables.
For global constants so do we.
And for what it's worth with CFMX+ there is NO REASON to lock the writing of global constants in any scope. Although you might want to add to the application variable sets some kind of test to see if they already exist so you only write them once when the application is initialised.
I would not use method 1 as its best practice to tell CF what type of
variables to use, other wise it has to search the variables scope to find
them.
Although for local variables it doesn't have to look far as they are the first scope searched. You can always prefix local vars with "variables." in any event.
I have come across some web hosting companies that don't allow application variables, so this might effect your choice.
The only reason for this shinanigans is the fear that incorrectly locked shared scope vars will cause memory corruption and kill the server. With CFMX+ this is no longer an issue.
-- geoff http://www.daemon.com.au/
--- 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/
