On 12/11/06, Aaron Roberson <[EMAIL PROTECTED]> wrote: > If you initialize all of your objects with the start of your > application then the user will have to wait until the objects are all > initialized before they can view any pages. As you know, CFC's are > pretty heavy and createObject, though it is better than cfinvoke, > still takes time. > > ANSWER: If the application waits two pages later, the visitor to your > site will not have to. I put my users first. > > -Aaron
I have to ask, how many objects are people trying to instantiate? I have maybe 8 or 9 objects to load into the application scope. I'll tell you right now that there wont be any noticeable savings doing with the initialization of the app or waiting until you need it. To make sure its understood, I'm talking about objects that will persist until the app times out. Not some thing that would be instantiated on every page load. I'm going to look for some decent example of a objectFactory and do some testing to see if there is a performance hit. I'm getting the feeling that people are starting to use objectFactories because its cool and new. Not because it will benefit the performance of their applications. And we all know that a high performance app makes the users happy. Phil ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:263662 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
