Would be interesting to se MX's version of results. I might run some tests later if I can be bothered [read as: have time]. But yes, I agree that CFSCRIPT is better at initialising variables than the corresponding CF tag, and that nested tag calls would benefit, though on an occasional basis with non nested tags I still wouldn't worry. At the end of the day you can get much better performance by writing web apps as pure Java servlets ;-)
Steve > -----Original Message----- > From: Adam Hope [mailto:[EMAIL PROTECTED] > Sent: 01 April 2003 09:30 > To: [EMAIL PROTECTED] > Subject: RE: [ cf-dev ] : [ cf-dev ] cfTag best practises template > > > Hi Steve, > > Our system uses lots of nested custom tags for the UI. In our > testing we > have been able to knock off over 80ms for every page request by moving > the CFPARAMs to CFSCRIPT. For us performance is everything and lots of > CFPARAMs per request is slower the CFSCRIPT. This is using both CF 4.5 > and CF 5, I've not had chance to try it on MX yet. > > I'm sure this will differ from site to site, I was just > trying to share > the stuff we have found. Don't get me started on WriteOutput either > (that is so slow its laughable). > > Adam. > > -----Original Message----- > From: Steve Martin [mailto:[EMAIL PROTECTED] > Sent: 31 March 2003 18:00 > To: [EMAIL PROTECTED] > Subject: RE: [ cf-dev ] : [ cf-dev ] cfTag best practises template > > > Adam, > I think you'll find that in the overall scheme of things that > any speed > differences between cfscripted variable testing and cfparam are > negligible. Have you got any metrics to prove that there could be an > issue? > > Steve > > > -----Original Message----- > > From: Adam Hope [mailto:[EMAIL PROTECTED] > > Sent: 31 March 2003 15:21 > > To: [EMAIL PROTECTED] > > Subject: RE: [ cf-dev ] : [ cf-dev ] cfTag best practises template > > > > > > I would avoid using cfparams and use cfscript instead. It > requires a > > fair bit more coding but CFPARAM is very slow. > > > > Adam. > > > > -----Original Message----- > > From: Steve Martin [mailto:[EMAIL PROTECTED] > > Sent: 31 March 2003 14:03 > > To: [EMAIL PROTECTED] > > Subject: RE: [ cf-dev ] : [ cf-dev ] cfTag best practises template > > > > > > Use a CFPARAM DEFAULT for params that you can assume a > trivial default > > > value for and CFPARAM TYPE for attributes that are required. > > > > For tags that pass back a value to the caller, allow the tag to be > > called with an attribute which contains the name of the > result to be > > placed in the caller scope. > > > > Comment code clearly (though we all do this all the time > anyway, yes! > > ;-] ) > > > > Steve > > > > > -----Original Message----- > > > From: Alex Skinner [mailto:[EMAIL PROTECTED] > > > Sent: 31 March 2003 13:19 > > > To: [EMAIL PROTECTED] > > > Subject: RE: [ cf-dev ] : [ cf-dev ] cfTag best practises template > > > > > > > > > Never really seen a best practices doc for cf tags > > > > > > I know the CF Advanced training material mentions that required > > > attributes should be checked for > > > and the list of attributes should be compared to expected > > > attributes so that > > > the user recieves an error if they pass > > > in an attribute the tag doesn't understand. > > > > > > Part from that just general best practices I suppose. > > > > > > Dug out an example comment from some docs part from that not sure > > > > > > Seans guide for the rest maybe > > > > > > <!--- > > > AUTHOR: > > > DATE: > > > PURPOSE: > > > ATTRIBUTES: > > > Name="..." -required > > > USAGE NOTES: > > > <cf_foo name="value"> > > > MODIFICATION LOG: > > > DATE AUTHOR MODIFICATION > > > ==== ======= ================================ > > > ---> > > > > > > > > > Alex > > > -----Original Message----- > > > From: Justin MacCarthy [mailto:[EMAIL PROTECTED] > > > Sent: 31 March 2003 12:33 > > > To: [EMAIL PROTECTED] > > > Subject: [ cf-dev ] : [ cf-dev ] cfTag best practises template > > > > > > > > > > What is it that you think you're doing badly? ;o) > > > > > > LOL > > > > > > > > Stephen > > > > > Just out of interest, does anyone know of a "best > > > practise" custom cfml > > > > > tag template??? > > > > > > > > > I don't remember ever having seen a best practices for > > > custom tags, just > > > > general CF ones. > > > > > > Yeah, I don't think I have either. Lots of general cf > coding style, > > > and Seans guidelines has some stuff, mostly var naming guidelines > > > > > > Just want to make sure the tags I'm written are best practise. > > > > > > Thanks > > > Justin > > > > > > > > > -- > > > ** Archive: > http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] For > > human help, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > ** Archive: > http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] For > > human help, e-mail: [EMAIL PROTECTED] > > > > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] For > human help, e-mail: [EMAIL PROTECTED] > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] For > human help, e-mail: [EMAIL PROTECTED] > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] For > human help, e-mail: [EMAIL PROTECTED] > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
