I am no pro with CFCs as I'm just learning them myself, but I believe the answer is yes, it will die after the page request is over. In the reading I've done, people will instantiate their CFCs into persistant variables such as server, session, or application scopes so that the instance of that CFC will be available to all page requests.
So, let's say for example, I have some CFC that I invoke methods on quite often. Instead of invoking it repeatedly in various pages, I might as will just invoke it once and save that instance in the application scope so it is accessible to every page. You still have to be cautious of locking, just like any other variable, though. hth, Mike Andy Mcshane wrote: > Just a quick question to help clear, hopefully, the last of the muddy waters > with regards to how CFC's work. > > A CFC that is initialized and stored within the application/session scope is > then available to use everywhere as required. > > Now I just want clarification on CFC's created at page level. If I create an > instance of a CFC on my page, carry out some processing and then do cflocate > to another page am I correct in assuming that my CFC instance is now gone and > if I wish to re-use it I must create another instance of it? I am just a > little confused on the whole lifecycle bit of CFC's, can anyone provide some > clarity? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:220880 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
