The 'search' for the tag, though, is done once. That's why if you move a custom tag after it has been called once, you need to restart MX for it to 'look' for it again.
That being said - I prefer cfmodule w/ template so I can specify exactly where MX should run the tag - this is extremely important for boxes where you may have multiple versions of the same tag. -Ray ---------- Original Message ---------------------------------- From: "Adam Churvis" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Fri, 19 Sep 2003 12:21:35 -0400 >> I'm all for enhancing performance, but the decision to use these is >> definitely architectural and shouldn't be impacted by performance >> concerns. > >I wholeheartedly agree, Jim. > >My point of contention was whether or not Sean thought that CFMODULE on CFMX >6.1 using template="" syntax was "slow" because we use custom tags quite a >bit here. Our custom tags often in turn call component methods that do all >the "heavy lifting," and the custom tags handle the display. CFMODULE >directly addresses each custom tag as it is used, it eliminates the "Little >Bo Peep" behavior of having to search for the custom tag being called, and >it completely eliminates occlusion in shared hosting environments where >custom tags may be named the same across different custom tag paths defined >in CF Administrator. > >I just really wanted to hear what Sean had to say about these things because >I respect his opinion very much, as I do yours. > >Respectfully, > >Adam Phillip Churvis >Member of Team Macromedia > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm?link=i:4:137689 Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com
