I'm not 100% on this but I believe when you use cfinvoke it creates an instance of the component on ever cfinvoke call. So if you are using cfinvoke on the same component, you would be better off creating an instance and invoking the methods that way.
On 5/31/07, Rick Root <[EMAIL PROTECTED]> wrote: > > On 5/31/07, Robertson-Ravo, Neil (RX) > <[EMAIL PROTECTED]> wrote: > > What about cfinvoking a method in an already persisted object, I.e. > Using > > component="#application.foo#" > > I personally can't think of any reason to use cfinvoke to call a > method of an already instantiated object. > > You couldj ust go > > <cfset results = application.foo.method()> > > or > > <cfscript> > results = application.foo.method(); > </cfscript> > > and either would be prettier than cfinvoke. > > IMO ;) > > Rick > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:279765 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
