> 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.
This can be overcome by extending your Application timeout. If your app
only gets hit once every two days, make the Application timeout three days.
Then in App.cfm you do something like
<cfif not isDefined("Application.myObject") or
isDefined("url.reloadObjects")>
<instantiate>
</cfif>
This way the object will not re-instantiate every time the page is hit, only
if it is not yet defined; or if you do want to explicitly reload your
objects, set the url variable "reloadObjects".
-- Josh
----- Original Message -----
From: "Aaron Roberson" <[EMAIL PROTECTED]>
To: "CF-Talk" <[email protected]>
Sent: Monday, December 11, 2006 2:23 PM
Subject: Re: whats the purpose of an objectFactory?
>> But why not go ahead and get the job done with the initial load of the
>> application? Why wait for it to happen two page loads later?
>
> 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
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:263659
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
