Custom tags allow you to encapsulate all your data.
What happens in the tag stays in the tag.
There is a slight performance issue, but I've been told it's very small.
(Hal Helms did some benchmarks on his website, but I've no idea where they
are).
Our rule of thumb for development if it takes inputs or if it returns
information it is called as a custom tag. This gives us 100% flexibility to
deal with any changes to graphics or functions without needing to worry at
all about affecting the program downstream.
We also only return 1 variable from a custom tag and the variable returned
has the name of the file it called (minus the ".cfm").
-----Original Message-----
From: Shane Witbeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 08, 2000 6:26 PM
To: fusebox
Subject: custom tags vs. cfincludes
Has anyone done any load testing or have any suggestions on whether to use
custom tags vs. cfincludes? We are implementing a site which uses several
custom tags and I was curious if there are performance issues with respect
to using one over the other. TIA
Sincerely,
Shane Witbeck
Webmaster
mailto:[EMAIL PROTECTED]
www.digitalsanctum.com
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
