Just testing things:

Test 1 (cfinclude)
------------------
<cfset tick = gettickcount()>
<cfinclude template="includetest.html">
<cfoutput><p><b>Include: #gettickcount() - tick#</b></p></cfoutput>

Test 2 (cffile)
---------------
<cfset tick = gettickcount()>
<cffile action="read" file="#expandpath("includetest.html")#"
variable="myfile">
<cfoutput>#myfile#</cfoutput>
<cfoutput><p><b>cffile: #gettickcount() - tick#</b></p></cfoutput>

I ran both once so everything was compiled then changed the html file
(once for each test).  The first test showed an execution time of around
700ms (showing compilation did happen, even for just a plain text file,
no markup at all) whereas the second was constantly around 0/1/2ms.  I
ran both tests a few times and got the same results each time.

So there: any <cfinclude>'d file appears to be compiled before it is
used.

Tim.


-------------------------------------------------------
RAWNET LTD - Internet, New Media and ebusiness Gurus.
Visit our new website at http://www.rawnet.com for
more information about our company, or call us free
anytime on 0800 294 24 24.
-------------------------------------------------------
Tim Blair
Web Application Engineer, Rawnet Limited
Direct Phone : +44 (0) 1344 393 441
Switchboard : +44 (0) 1344 393 040
-------------------------------------------------------
This message may contain information which is legally
privileged and/or confidential.  If you are not the
intended recipient, you are hereby notified that any
unauthorised disclosure, copying, distribution or use
of this information is strictly prohibited. Such
notification notwithstanding, any comments, opinions,
information or conclusions expressed in this message
are those of the originator, not of rawnet limited,
unless otherwise explicitly and independently indicated
by an authorised representative of rawnet limited.
-------------------------------------------------------


> -----Original Message-----
> From: Douglas Humphris [mailto:[EMAIL PROTECTED] 
> Sent: 29 July 2003 10:48
> To: [EMAIL PROTECTED]
> Subject: RE: [ cf-dev ] MX Compilation
> 
> 
> Eh? That's what I said. Don't put cfoutput around the html 
> and CF will ignore it. Perhaps I didn't explain myself very well. D
> 
> -----Original Message-----
> From: Tom Smith [mailto:[EMAIL PROTECTED] 
> Sent: 29 July 2003 10:43
> To: [EMAIL PROTECTED]
> Subject: Re: [ cf-dev ] MX Compilation
> 
> that's not entirely true... IIRC
> 
> any thing you cfinclude will be run as if it's a cf page, so 
> a standard HTML page will be fine, unless the colour code in 
> the HTML page has <cfoutput> tags around it.
> ----- Original Message ----- 
> From: "Douglas Humphris" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, July 29, 2003 10:37 AM
> Subject: RE: [ cf-dev ] MX Compilation
> 
> 
> Hi Tim,
> CF is going to treat the included html just as much as 
> treating the "in-file" html. If there's anything in the html 
> that CF might compile but you don't want it to (e.g. 
> color="#FFFFFF") then don't put CFOUTPUT tags around the 
> cfinclude, otherwise you should be fine.
> 
> Douglas
> 
> -----Original Message-----
> From: Tim Blair [mailto:[EMAIL PROTECTED]
> Sent: 29 July 2003 10:32
> To: [EMAIL PROTECTED]
> Subject: RE: [ cf-dev ] MX Compilation
> 
> 
> > Unless you include the .html in a .cfm page first.
> 
> That's the one...  E.g...
> 
> includetest.html:
> some random stuff
> 
> And then...
> 
> includetest.cfm:
> <cfinclude template="includetest.html">
> 
> Vs.
> 
> includetest.cfm:
> <cffile action="read" file="#expandpath("includetest.html")#"
> variable="myfile">
> <cfoutput>#myfile#</cfoutput>
> 
> 
> -------------------------------------------------------
> RAWNET LTD - Internet, New Media and ebusiness Gurus.
> Visit our new website at http://www.rawnet.com for
> more information about our company, or call us free
> anytime on 0800 294 24 24.
> -------------------------------------------------------
> Tim Blair
> Web Application Engineer, Rawnet Limited
> Direct Phone : +44 (0) 1344 393 441
> Switchboard : +44 (0) 1344 393 040
> -------------------------------------------------------
> This message may contain information which is legally 
> privileged and/or confidential.  If you are not the intended 
> recipient, you are hereby notified that any unauthorised 
> disclosure, copying, distribution or use of this information 
> is strictly prohibited. Such notification notwithstanding, 
> any comments, opinions, information or conclusions expressed 
> in this message are those of the originator, not of rawnet 
> limited, unless otherwise explicitly and independently 
> indicated by an authorised representative of rawnet limited.
> -------------------------------------------------------
> 
> 
> 
> -- 
> ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
> 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED] For human help, e-mail: 
> [EMAIL PROTECTED]
> 
> 
> 
> 
> -- 
> ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
> 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED] For human help, e-mail: 
> [EMAIL PROTECTED]
> 
> 
> -- 
> ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
> 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED] For human help, e-mail: 
> [EMAIL PROTECTED]
> 
> 
> 
> 
> -- 
> ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
> 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED] For human help, e-mail: 
> [EMAIL PROTECTED]
> 
> 
> 



-- 
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]

Reply via email to