> Please guys tell me if I'm wrong, fusebox idea is to put the
> maximum number of templates in a single one right? Like: I
> have a page that adds, deletes, and modifies data from a table.
> Using the fusebox concept it would be like this:
>
> <cfif fuseaction EQ add>
> add...
> <cfelseif fuseaction EQ del>
> del...
> <cfelse>
> update
> </cfif>
>
> right? well the CF server must read the entire template and
> then perform the correct action. Now without the fusebox
> concept: I have a page called add.cfm, del.cfm and upd.cfm
> with no Ifs and elses on it, so I guess It's pretty much
> faster right?

It will probably be slightly faster to just specify your three scripts
instead of using Fusebox. However, the difference will probably be so small
as to be completely insignificant. CFINCLUDEs are relatively inexpensive
operations, once all the scripts have been cached in memory.

In any case, that's not really the right question to ask. Any code
reuse/maintenance methodology, properly implemented, will perform less well
than the alternative of not using that methodology, all other things being
equal. When you get right down to it, you'd get better performance writing
ISAPI filters to do everything, instead of using CF at all. The right
question, in my opinion, would be "Does the maintenance benefit of using
this methodology outweigh the performance cost?" Not being a big fan of
Fusebox myself for the types of applications Fig Leaf does, I'd say no. But
that's because my development and maintenance goals don't match with those
of Fusebox, not because I think it's "slow". If my goals and Fusebox's goals
overlapped more, then I'd use it.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444

------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to