It's just a question of preference. I chose CFSAVECONTENT over the CFXML due to familiarity but after reading your mention and looking it up, CFXML might be better, even with using the toString() function after it (another operation).
> Hi Michael, > > Is this one of the opinion questions you ask where you already know > your own answer? :) > > I'd use the CFSaveContent method, but using CFXml instead of > CFSaveContent - works the same, but validates the XML and created an > XMLDocument object that can by turned into a string via toString(). > > -Joe > > On 10/11/05, Michael Dinowitz <[EMAIL PROTECTED]> wrote: >> In running through a shopping cart codebase (cartweaver), I decided to >> change a chunk of 40 or so CFSET operations into a single CFSAVECONTENT >> block. As this was for building an XML packet, it looked logical to me. >> No real savings in code size but to me it just looked cleaner and looked >> like 'less' operations. >> >> Question: What is your preference in such situations. Multiple CFSETs >> with each adding a new line of XML to the variable or a block of >> CFSAVECONTENT with the entire block wrapped in a CFOUTPUT? >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:220696 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
