The existence of the file, itself, is nothing. It's like a millionth of a second or
so. But what's IN the file, now that's where the lag could occur. The possibilities
are endless here.
I would recommend for a large site that you look into the Fusebox methodology. You
can separate out local variables (within the sub apps) from global variables (which
you store in a app_globals file) so that you only create overhead for the applicable
section and not the entire application.
---mark
--------------------------------------------------------------
Mark Warrick
Phone: (714) 547-5386
Efax.com Fax: (801) 730-7289
Personal Email: [EMAIL PROTECTED]
Personal URL: http://www.warrick.net
Business Email: [EMAIL PROTECTED]
Business URL: http://www.fusioneers.com
ICQ: 346566
--------------------------------------------------------------
> -----Original Message-----
> From: Kevin Miller [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 05, 2000 3:02 PM
> To: [EMAIL PROTECTED]
> Subject: Application.cfm location costs?
>
>
>
> Does anyone have any benchmarks on the overhead incurred by
> putting the application.cfm file at the root of the web server,
> 1-2 levels above the application files?
>
> We are trying to develop a site-wide framework, and we are
> debating whether it is better to have one application.cfm at the
> root of the server or one in each application directory that
> cfincludes the one at the root.
>
> Thanks,
>
> Kevin Miller
> Vascular Chief Technologist
> Medtronic Vascular
> [EMAIL PROTECTED]
> (707) 566-1200
>
> ------------------------------------------------------------------
> ------------
> Archives: http://www.mail-archive.com/[email protected]/
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=sts&body=sts/cf_tal
> k or send a message to [EMAIL PROTECTED] with
> 'unsubscribe' in the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/cf_talk or send a message
to [EMAIL PROTECTED] with 'unsubscribe' in the body.
