You can most certainly store the datasource in an application variable.
Assuming you have a whole bunch of app vars that you will be using
throughout your application. Andrew is correct in what he is saying
about using request scope as you don't need to lock the application
scope EVERY time you want to use it.
Instead you can use something like:-
<cflock scope="APPLICATION" type="READONLY" timeout="10"
throwontimeout="Yes">
<cfset Request.Application = duplicate(Application)>
</cflock>
Martin Parry
Macromedia Certified Developer
http://www.BeetrootStreet.co.uk
-----Original Message-----
From: Andrew Grosset [mailto:[EMAIL PROTECTED]
Sent: 29 December 2004 05:16
To: CF-Talk
Subject: Re: STICKY Application.datasource
Unless it's really necessary I would try not to set "datasource"
as an application variable, either:
<cfset datasource="CODAGenomics">
or
<cfset request.datasource="CODAGenomics">
Andrew.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Special thanks to the CF Community Suite Silver Sponsor - CFDynamics
http://www.cfdynamics.com
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188919
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
