Speed really depends on whether caching is available or not. CF itself
uses the ladder method. Any time you use <CFINCLUDE> the code is treated,
and loaded, as part of the same, huge, page (index.cfm), even if that
particular <CFINCLUDE> or fuseaction is not used in that page request. But
with CF caching, it's already loaded into memory, so it is actually even
faster than if it had to go find that file, open it, read it and interepret it.
The main difference is that with server side includes like ASP uses, the
web server is assembling the files into a single page, and then passed to
ASP, but with <cfinclude>, it is happening in the CF server.
With the ASP Server.Execute Method, this would happen in the ASP engine.
Does ASP 3 have a caching facility that applies to the execute method? If
yes, use Server.Execute. Does your web server cache pages? If yes, then
use the server side include method.
At 12:42 PM 5/17/01, Scott Van Vliet wrote:
>I have been led to believe that it is quicker
>and more efficient than the ladder method.
>
>** Scott
>
>-----Original Message-----
>From: David Crowther [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, May 17, 2001 8:49 AM
>To: Fusebox
>Subject: RE: Fusebox ASP only on Win2K?
>
>
>What is the difference between these two methods? Is one quicker than the
>other?
>
>...david
>
>-----Original Message-----
>From: Scott Van Vliet [mailto:[EMAIL PROTECTED]]
>Sent: 17 May 2001 4:16 PM
>To: Fusebox
>Subject: Re: Fusebox ASP only on Win2K?
>
>
>When I say, dynamically include pages, I mean:
>
><%
>strPage = "act_adduser.asp"
>Server.Execute(strPage)
>%>
>
>In ASP 2.0, you could...
>
><%
>Select Case fuseaction
> Case "searchform"
>%>
> <!--#include file="dsp_searchform.asp"-->
><%
> Case "searching"
>%>
> <!--#include file="act_searchform.asp"--> <!--#include
>file="dsp_searchresults.asp"--> <%
> Case Else
>%>
> <!--#include file="dsp_about.asp"-->
><%
>End Select
>%>
>
>To dynamically include a page...
>
>
>
>----- Original Message -----
>From: "Scott Van Vliet" <[EMAIL PROTECTED]>
>To: "Fusebox" <[EMAIL PROTECTED]>
>Sent: Thursday, May 17, 2001 7:44 AM
>Subject: Re: Fusebox ASP only on Win2K?
>
>
> > In previous versions of ASP, there wasn't a way to dynamically
> > include pages into a file. In ASP 3.0, Server.Execute was introduced,
> > which is basically the same thing as <cfinclude>.
> >
> >
> > Scott
> >
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > :: Scott Van Vliet ::
> > :: Senior Web Engineer ::
> > ::....................................::
> > :: JUXT Interactive ::
> > :: 858 Production Place ::
> > :: Newport Beach, CA 92663 ::
> > :: Phone > 949.752.5898 x.202 ::
> > :: Cell > 714.469.6805 ::
> > :: Fax > 949.574.5922 ::
> > :: Email > [EMAIL PROTECTED] ::
> > :: Web > www.juxtinteractive.com ::
> > > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> > ----- Original Message -----
> > From: "Kay Smoljak" <[EMAIL PROTECTED]>
> > To: "Fusebox" <[EMAIL PROTECTED]>
> > Sent: Thursday, May 17, 2001 6:59 AM
> > Subject: Fusebox ASP only on Win2K?
> >
> >
> > > My company is about to take on an ASP project. We were planning on using
> > > Fusebox. I was browsing
> > > http://www.meta-magic.com/cgi-bin/fusewiki?AspFuseBox and I noticed it
> > says
> > > "ASP Fusebox is possible with ASP 3.0. That means IIS 5.0 ... and
>Windows
> > > 2000". What is the reason for this? Is fusebox not possible at all in
> > > previous versions of IIS?
> > >
> > > Thanks,
> > > K.
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
