easier to re-initialize some of the application variables, example;
<cfset application.setting.dsnMain = "myDSN">
<cfset application.setting.mailServer = "my.mail.com">
<cfset application.setting.emailSupport= "[EMAIL PROTECTED]">
Now if you need to reinitialize these settings you simple do
<cfset structDelete(application, "setting")>
and they are all gone.
Same for session variables
<cfset session.userInfo.fullName= "myDSN">
<cfset session.userInfo.pkIDUser= "my.mail.com">
<cfset session.userInfo.email= "[EMAIL PROTECTED]">
<cfset structDelete(session, "userInfo")>
and they are all gone.
Taco Fleur
Blog <http://www.tacofleur.com/index/blog/>
http://www.tacofleur.com/index/blog/
Methodology http://www.tacofleur.com/index/methodology/
Tell me and I will forget
Show me and I will remember
Teach me and I will learn
-----Original Message-----
From: Bob Haroche [mailto:[EMAIL PROTECTED]
Sent: Monday, 8 March 2004 10:24 AM
To: CF-Talk
Subject: Newbie Locking Question
Using CF 5...
If I set an Application variable once in Application.cfm that is
(theoretically) never going to change, eg:
<cfset Application.DNS = MyDNS>
Do I really need to place "read only" locks around every query in the
application that wants to access that database? I could see the need
to do that if the Application.DNS were ever going to be re-written,
but assuming it's not going to be, is there harm in forgoing the lock?
-------------
Regards,
Bob Haroche
O n P o i n t S o l u t i o n s
www.OnPointSolutions.com
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
