You know you enjoy thumbing out the experience nuggets to youngsters like myself ;). I bet you even had to restrain yourself to not type out an in-depth, totally enlightening treatise of the real innerworkings of cfinvoke.
On Sat, Mar 14, 2009 at 6:20 PM, Jared Rypka-Hauer <[email protected]>wrote: > Thanks for saving me the effort... ;) KIDDING! > I had to, just had to. > > J > > On Mar 14, 2009, at 5:45 PM 3/14/09, David McGuigan wrote: > > That was idiotic. Sorry. It's like the 2nd paragraph of the documentation. > > > On Sat, Mar 14, 2009 at 4:43 PM, David McGuigan > <[email protected]>wrote: > >> Quick question. >> >> <cfinvoke/> lets you call a CFC's method "without instantiating the owner >> CFC". >> >> That's a white lie right? Does cfinvoke just do the instantiation in the >> background and toss the instance afterward or is the method somehow called >> semi-staticly? >> >> My real question/concern is about performance. >> >> I have a code situation in which I will be able to accomplish what I want >> by instantiating a component, feeding it arguments with a instance.method( ) >> style invocation, and then never using the instance again, but I'm wondering >> if cfinvoke is somehow so magical that by using it w/ an argument collection >> I would reap significant performance benefits. ??!? >> >> Thanks. >> > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
