One reason: Custom tags execute in their own memory space, so performance
will be worse with his method than with simple cfincludes.
-----Original Message-----
From: Shane Johnson [mailto:[EMAIL PROTECTED]]
Sent: March 29, 2001 5:22 PM
To: Fusebox
Subject: Tell me what I should tell him....
Hey all,
I was going over a fusebox site in development with a friend and
noticed
he was doing something that I don't see done anywhere else. Rather than
using <cfinclude> in his index.cfm he is calling his includes as custom
tags. so <cfinclude template = "dspDoggie.cm"> becomes <cf_dspDoggie.cfm>.
Now this works as CF will look in the immediate directory for a tag before
going to the custom tag directory but it just seems very wrong.
Unfortunatley I was unable to articlate why it is wrong to do it this way.
Can I get some logical arguments to this effect so I can get back to him
with a logical explanation?
Shane Johnson
Coldfusion Developer
Fusebox [XFB]
www.strangetactics.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
