Does
anyone actually have definitive information on how exactly evaluate runs slower
and whether it is the command itself or the fact that it is dynamic. Also, does
anyone have comparible "costs" to run an evaluate vs. say instantiating a 400
line object?
---------------------------------------------------------------Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RADEMAKERS Tanguy
Sent: Thursday, May 18, 2006 4:00 AM
To: CFCDev@cfczone.org
Subject: RE: [CFCDev] CFINVOKE vs. Evaluate<cfinvoke component="#obj#" method=#FunctionName# returnvariable="foo" /> has to be interpreted at run time as well. There's nothing to say that the value of #obj# and #FunctionName# are known before then./t----------------------------------------------------------Isn't the reason behind the slower processing that it can't be compiled like the rest of the code? It must be interpreted at run-time for each request?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Roberts
Sent: Wednesday, May 17, 2006 8:18 PM
To: CFCDev@cfczone.org
Subject: Re: [CFCDev] CFINVOKE vs. Evaluate
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
