Kevin!)
I was trying not to overload people with too many syntax-y things, so I
tried to stay away from too much talk about the 16 different ways we have to
deal with components. I only succeeded in 1.5 out of 3 talks. :-)
You *can* use cfinvoke for both CFCs and Web service objects after calling
cfobject and passing the result of that as the Component= or WebService=
attribute. As Ray said, this gives you the same reuse as the obj =
CreateObject()/obj.foo() syntax. Or you can mix and match.
Its simply a style issue. Even the reuse of a CFC object I don't think will
have that big of a performance impact (depending on the CFC), but its nice
to do.
Note however that in the web service case, the object is a bit more heavy
weight, so you *want* to reuse it as much as possible if you are calling
more than one operation on a page.
Hope that helps.
--
Tom Jordahl
Macromedia
-----Original Message-----
From: Kevin Graeme [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 12:40 PM
To: CF-Talk
Subject: Re: Since CF knows no nulls...
> > I don't know if this is specifically why, but my notes from a
> > MAX session mention that using cfinvoke slows things down because
> > it needs to create and manage a new object for each call, and
> > it was recommended to reuse existing objects where possible.
>
> In the absence of reuse, though, it doesn't make any difference whether
you
> use CFINVOKE or CreateObject. In many cases, there may not be any reuse.
Just double-checked the slides and the speed comparison was specifically for
creating an object vs reusing an object. Not which syntax was used to do so.
Either my notes from the talk were incomplete or the speaker glossed over
some of the issues. I think what was catching me, and maybe Tom, was
thinking of cfinvoke as for creating new objects.
-Kevin
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
