on 3/17/03 12:27 PM, Raymond Camden at [EMAIL PROTECTED] wrote: > Correct, becuase my 'core' Application.cfm will contain site-wide logic, > but I have a specific need for this particular subfolder. So, unlike > most Application.cfm files, you won't see a <cfapplication> tag in it. > We aren't defining a new application, just some logic to run for one > particular folder. > > Hope this makes sense.
It's starting to make perfect sense. If I have a subdirectory in the root that I want to protect, and I want code to run every time a page in that subdirectory is accessed, then I want to stick that code in an application.cfm. I can pass session information from the root application.cfm, to the lower application.cfm, so I can use the root application to process login information, and set the sessions, and use the lower application.cfm to check for the existence (getAuthUser()) of a logged in user and if that doesn't exist, then pass them back up to the index.cfm of the root directory... Am I heading in the right direction? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
