Title: Message
I noticed all the discussion about removing whitespace.
 
We're currently in Beta on a new tool named LoRCAT, the Load Reduction and Concentration Analysis Tool for ColdFusion, that should be of great interest to Fusebox coders because of its ability to increase performance and finitely analyze both existing and potential performance bottlenecks on a template-by-template basis -- even when one is called iteratively from another or CFINCLUDEd as elements of a page. 
 
LoRCAT intelligently strips all comments (of all kinds) and whitespace from a safe copy of your code, which increases performance significantly in most cases.  LoRCAT also generates detailed graphical reports of every element of load your application generates, which shows you precisely where to optimize your code.
 
If one or two of the more dedicated Fusebox coders on this list would like to Beta test the next release then please contact me _offline_.

Respectfully,
 
Adam Phillip Churvis
Certified Advanced ColdFusion 5 Developer
Productivity Enhancement, Inc.
http://www.ColdFusionTraining.com
E-mail:  [EMAIL PROTECTED]
Phone:   770-446-8866
----- Original Message -----
Sent: Tuesday, June 11, 2002 9:20 PM
Subject: RE: how to use LessWhiteSpace

Hi Bartee.
 
Yes, that is indeed the syntax for using CF_LessWhiteSpace, but if you use it just like that, it won't have any effect on any whitespace generated by the FB3 core, which would all be *outside* the CF_LessWhiteSpace tags.
 
On the other hand, as has been pointed out, the FB3 core is pretty clean in terms of generating unwanted whitespace, so I don't think you need to worry.
 
I also agree with Erki who said that these kinds of whitespace stripper add a performance hit to your requests, so I don't use this tag very much myself.  I only use it in very specific instances where I have a whitespace problem (usually caused by my own code, not by FB3), and where I can't justify the time and effort required to create the perfect <cfsettings>/<cfsilent> solution.  Sometimes you can spend hours banging your head around, trying to find out where that stray blank line is coming from. 
 
In these cases, I wrap CF_LessWhiteSpace tags around the smallest chunk of code possible, because the very modest performance hit does escalate as more HTML code is enclosed.  If I can isolate the particular dsp fuse culprit then I'm usually happy to just wrap that fuse's code in CF_LessWhiteSpace and proceed to more important matters.  At some later time, if the app is not performing as well as required, and if performance profiling shows that the whitespace stripping is a significant contributor, then I will revisit the problem area.
 
In general, do it the easy way first, then optimise as necessary.  Luckily, with FB3, the easy way is usually the *best* way too.  I guess that's the mark of a great architecture ;-)
 
Thanks,
LeeBB
-----Original Message-----
From: Bartee Lamar [mailto:[EMAIL PROTECTED]]
Ok, I down loaded Lee's less white space.
 
Do you use it??
 
<cf_lesswhitespace>#fusebox.layout#</cf_lesswhitespace>
 


IMPORTANT NOTICE:

This e-mail and any attachment to it is intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it.

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to