overwriting a component reference variable

> So if your right then a thousand iteration loop with each iteration > doing a cfinvoke will cause the template request to keep growing in > memory usage. There is no resource re-usage in the request. That would be my expectation. > This also means that the statement "after a method is invoked using > cfinvoke, the component instance is destroyed" is not 100% true. It is > destroyed, but nothing is gained by the destruction. I was always > under the impression that using cfinvoke was 'less costly' than > creating a variable to contain a component instance. :( The ideal response would be to say "marked for deletion" instead of "destroyed". But from the programmer's perspective, the component will not exist. I suspect it is less costly to invoke a method directly, as there is a cost to creating a reference. I don't want to speculate on how much less costly it is, though. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite.