Sean, Thanks for your reply! :)
I'd like to get your opinion on something else, if I may. If a system makes extensive use of a good-sized library of custom tags throughout an application (virtually on every page), and the logic and display tasks handled by them are truly best implemented as custom tags (many of which internally call components that interface with the persistence layer), wouldn't using CFIMPORT on every page (which redundantly re-imports the entire library of custom tags with each page request) be considered a second-best approach in favor of discrete calls via CFMODULE template="" to just those custom tags needed on each page? I can see using CFIMPORT for the occasional call to a custom tag in a relatively small library (or subdirectory of a library) of custom tags, but it seems to me that when you have a lot of them and use them just about everywhere that CFMODULE template="" is the best approach, both from an architectural and a performance point of view. I'm really interested in hearing your thoughts on this. I really respect you and your opinions. Thanks in advance. Respectfully, Adam Phillip Churvis Member of Team Macromedia Advanced Intensive ColdFusion MX Training ColdFusion MX Master Class: September 22 - 26, 2003 http://www.ColdFusionTraining.com Download CommerceBlocks V2.1 and LoRCAT from http://www.ProductivityEnhancement.com The ColdFusion MX Bible is in bookstores now! ----- Original Message ----- From: "Sean A Corfield" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Friday, September 19, 2003 7:24 PM Subject: Re: So... cfmodule is slow...? > On Friday, Sep 19, 2003, at 09:21 US/Pacific, Adam Churvis wrote: > > 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. > > "slow" in comparison to, say, CFC method invocation. > > You must remember that these coding guidelines are written from the > perspective of my team's software experience which, in general, leans > toward CFCs instead of custom tags and, where we use custom tags, we > like to tightly control their use - hence the recommendations for > cfimport to identify the path to the tags and to create unique > 'namespaces' to invoke the custom tags. > > And, as Jim says, this is more of an architectural decision than a > performance based one. > > Sean A Corfield -- http://www.corfield.org/blog/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm?link=i:4:137785 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
