I've been at a loss as to find information on the best way to handle my application's cfcs and config variables ... and from other threads I've read, I think there's probably a few of you here who can help ...
At present, I configure a whole bunch of settings/structures in the application scope (in application.cfm) just the once for each lifetime of the application.
>From what I read in an article I located (sorry I dont have it here) - this was fine to do, and I could read/reference the application scope variables directly through my site without having to lock them (as they are used for read only - there is never any writing). Does this seem fine so far? and if so, also reading/referencing them from within cfcs?
The other issue (the main one!) is that in my application.cfm file, I am creating my cfc objects within the application scope. eg:
application.objTimetable = createObject("component", "#application.components#.timetable") ;
The theory being that they are created once and stored in memory for any page to access/utilise at any time - however my concern is are they multi-thread accessible? what other issues are there??
I dont want to have to create a new instance of an object each time I enter the page (ie request scope) and I dont want to store the object in the session scope either (meaning every user logged in has there own object instance!), so that's where I figured storing in the application scope!
Any help or advice would be extremely appreciated
Thanks
Leigh
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
