Sounds like it'd be trouble enforcing/maintaining that. How many people do you have that may change the app name? How has it worked out for you?
Ade -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 25 January 2006 13:45 To: CF-Newbie Subject: Re: Dynamically setting datasource One of the problems faced with the discussion on this topic is that the application name variable is the same for all versions of the software. We have adopted a simple solution to this. Each release of the software is given a distinct application name with a version number attached. BFD_CTMGR would be BFD_CTMGR_010 for production and BFD_CTMGR_011 for the current version in the TEST system and BFD_CTMGR_012 for the current development environment. This prevents application variables from accidently being shared on the same box. Everytime a new version of software is started the version number is incremented in DEV. -------------- Original message -------------- From: Stephen Moretti <[EMAIL PROTECTED]> > Nick Sweeney wrote: > > Thanks Ade, > > > > So - what that means is: > > > > If have two clients both running Fat Admin on the same server - but two > > different URLS. > > > > www.client1.com > > > > www.client2.com > > > > And if they happen to run it at the same time - there is going to be issues > > of some kind. Like - they may cross over and use eachother's datasources???? > > > Correct. Or overwrite one another. > > > Because I set everything up in the app.cfm - > > > > > > > > > > > > > > > > > > name="BFD_CTMGR" > > sessionmanagement="yes" > > setclientcookies="yes" > > sessiontimeout="#CreateTimeSpan(0, 0, 120, 0)#"> > > > > If that's true - then a great example of a rookie mistake and quite eye > > opening. It was my understanding that this was running at the "browser" > > level - and not at the server - but I am wrong, aren't I. > > > All variables (apart from cookies) are actually created and stored on > the server in some way shape or form. Server, Application and Session > scopes are what I know as shared-scope variables. They are all stored > on the server, so you need to be very careful about application names, > protecting against race conditions and basically any situation where > more than one browser could potentially be accessing a variable in those > scopes. > > An easy fix for your current problem is probably just to replace the > dots in cgi.server_name with underscores and use that as part of your > application name. > > Regards > > Stephen > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:15:1593 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/15 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:15 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.15 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
