> >----- Original Message ----- > >From: "Douglas Smith" <douglas@teratech.com> > > > Hey, that's nothing if you consider how a Fusebox application is cached in > > > CF. All the cfincludes are *really* part of the same great big cached > > > page, so you are really caching a lot more than the index page when you do > > > a Fusebox application!
This doesn't sound right. But let's assume this is true, just for a second. That still means that what is cached is the <CFcase> which was true the last time the index page was hit; it can't possibly include the non-true <cfcase's> otherwise it should throw an error if you make a mistake in any one included fuse that isnt even the current fuseaction, right? .
Mike Dinowitz would know a lot more about this, but most switch statements (in CF or otherwise) would as part of their optimization only compile against the value's in the CFCASE's as a hash table pointing to the code within each CFcase rather than including it all--otherwise performance of the CFSWITCH would be the same as the series of <CFELSEIF>'s that it effectively replaces.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Fusebox
John Quarto-vonTivadar