The idea is that you store all the information required for application init (such as app name and timeout, session timeout etc) in an external file, so if you need to change it for any reason you can do so without modifying the code - it also helps with app reuse because you can use the same application multiple times, just by changing the config file.
fair enough, apologies for leaving my brain at home, I'm currently trying to disect a database with 644 tables so I'm a bit out of it to be honest.
I have done similar myself to achieve application re-use, though I used the server scope to cache the application initialisation settings.
Mark
-- These lists are syncronised with the CFDeveloper forum at http://forum.cfdeveloper.co.uk/ Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
CFDeveloper Sponsors and contributors:-
*Hosting and support provided by CFMXhosting.co.uk* :: *ActivePDF provided by
activepdf.com*
*Forums provided by fusetalk.com* :: *ProWorkFlow provided by proworkflow.com*
*Tutorials provided by helmguru.com* :: *Lists hosted by gradwell.com*To unsubscribe, e-mail: [EMAIL PROTECTED]
