In the end, it depends on what is meant by "only processes code that is
between CF tags".
If you are talking about the BUILT-IN webserver - then it depends on how
the webserver decides to process the file - but may not be relevant because
the web server and CF are all running in the Java machine and are
effectively a single application.
For example......
If it says ".CFM - hmmmmm - must be a Cold Fusion file - I will call the
Cold Fusion process and let it have its way" (then the CF process will have
to parse the whole thing anyway to find a CFOUTPUT tag). �This would mean
that the CF process is always invoked for a URL with a CFM file.
If it says "Hrmmmmm - I will parse this HTML/XML and any thing that starts
with a <CF I will pass on to the Cold Fusion process" - there MAY be some
speed improvement by using multiple <CFOUTPUT> tags.
HOWEVER......
If CF is running as an extension to IIS (or Apache) then a specific module
is invoked for the CFM extension (or any other extensions that you have
said require CF processing). �In this case, CF gets complete control of the
file from the beginning.
In either case, from what I can tell on reading up about the CF
architecture, it is using third-party parsers for XML - maybe it is also
using them for it's own tags (it would seem that way because of how the new
<CFIMPORT> works). �Therefore, processing a <CFOUTPUT> only means as it has
done in the past.......... CF must also process/parse #variable#
declarations. �Once it sees a <CFOUTPUT> it has to do this anyway - and
wont be any quicker if you put one ## or hundreds of them. �It all depends
on WHAT you put in there that will dictate the speed of it.
REMEMBER.....
If it is a CFM file then SOMETHING has to be looking for all the <CF....>
tags - the only additional overhead for a <CFOUTPUT> is that it has to also
parse/process the all ## items it finds.
Gary Menzel
IT Operations Brisbane -+- ABN AMRO Morgans Limited
Level 29, 123 Eagle Street BRISBANE QLD 4000
PH: 07 333 44 828 �FX: �07 3834 0828
[EMAIL PROTECTED] wrote on 01/08/2003 02:18:02 PM:
> I would guess that the performance hit is marginal and I personally
> prefer to have cfoutput outside loops and blocks of code rather than
> using multiple instances. My preference comes finding lots of cfoutput
> tags quite distracting, they seem to hide or camouflage the variables in
> use.
>
> I guess we need to know what *exactly* is going on when the <cfoutput>
> tag is encountered...
>
> One thing I have learned from this discussion is what to use instead of
> 'evaluate'. I guess I always knew that collections (like 'form') were
> structures but I never understood that I could use form[reference] to
> access the elements. Thanks to Steve for that little gem.
>
> Brett
> B)
>
> Adam Chapman wrote:
> > ok well i'll bite seeing as youre in
> > an agumentative mood today ;P
> >
> > As Chistopher explained his client wanted to
> > ba able to update 20 or so records at a time,
> > therefore cf would have to parse the code for
> > 20 or so cfoutput tags. I put this question to
> > you my good man.. Is it quicker for cf to
> > parse the code for 20 cfoutput tags or use 1
> > cfoutput and have cf process some extra html??
> >
> > Personally (in this case) i would use the 1 cfoutput tag..
> > but thats just what spins my wheels.. I have
> > no performance data to back up my reasoning.
> >
> > Anyone else care to comment/argue?
> >
> > Adam
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Steve
Onnis
> > Sent: Wednesday, 8 January 2003 2:11 PM
> > To: CFAussie Mailing List
> > Subject: [cfaussie] RE: Multiple Updates in forms (Compleat Code)
> >
> >
> > I bed to differ on pont (2) adam
> >
> > You should you CFOUTPUT as less as possible.
> >
> > I would have gone for somethinh mor like
> > -----------------------------------------
> > <form name="form1" method="post" action="testprice2.cfm">
> > <input name="totrows" type="hidden" id="totrows"
> > value="<cfoutput>#gtProds.recordCount#</cfoutput>">
> > � <cfloop query="gtProds"><cfoutput>
> > � � � <input type="text" name="field_#currentrow#"
> > value="#LSNumberFormat(gtProds.RetailPrice,',99999999999999.99')#">
> > � � � <input type="hidden" name="prodID_#currentrow#"
> > value="#gtProds.prodID#"></cfoutput>
> > � � � <BR>
> > � </cfloop>
> > <input type="submit" name="Submit" value="Update">
> > </form>
> > ----------------------------------------
> >
> > or even further, only put outputs around the actual variable.
> >
> >>From what I have seen, putting CFOUTPUT around large blocks of code
like
> > that will actually increase processing times as the whole chunk of code
> > needs to be processed by the CF server.
> >
> > Correct me if I am wrong, and this may be different under MX, but I was
> > under the understanding that CF only processes code that is between CF
tags.
> > If I am correct, by placing CFOUTPUT around large chunks of code, you
are
> > handing code to the CF server that it does not need to process as the
web
> > server will handle the HTML components of the processing.
> >
> >
> > Regards
> >
> > Steve Onnis
> > Domain Concept Designs
> > +61 422 337 685
> > +61 3 9444 7504
> >
> > http://www.domainconceptdesigns.com
<http://www.domainconceptdesigns.com>
> >
> > ("If you think it can't be done, you haven't asked me!") - Steve Onnis
> >
> >
> >
> >
> >
> > ---
> > You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
> > To unsubscribe send a blank email to leave-cfaussie-3452O@lists.
> daemon.com.au
> >
> > MX Downunder AsiaPac DevCon - http://mxdu.com/
> >
>
>
> --
> Brett Payne-Rhodes
> Eaglehawk Computing
> t: 618 9371-0471
> f: 618 9371-0470
> m: 0414 371 047
> e: [EMAIL PROTECTED]
> w: www.ehc.net.au
>
>
> ---
> You are currently subscribed to cfaussie as:
[EMAIL PROTECTED]
> To unsubscribe send a blank email to
[EMAIL PROTECTED]
>
> MX Downunder AsiaPac DevCon - http://mxdu.com/
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
