Yeah I agree Ben. Stripping the excess chars then processing the witango code should take just as much time or longer than if the excess chars were left in and then the code was processed.
I'm not sure how the code is cached but I bet once it's cached it might run a tiny bit faster and use a little less memory. A very tiny amount of bandwidth would be saved too probably. Maybe this is a "prettyness" issue though about not making the output html look ugly? On 1/25/07, Ben Johansen <[EMAIL PROTECTED]> wrote:
But, isn't the time to run this tag directly proportional to the extra time the non optimize code takes, yielding the same time to process the code an maybe more time due to optimize overhead Ben On Jan 25, 2007, at 9:18 AM, William M Conlon wrote: <@optimize [string]></@optimize> default string is tab, space, linefeed, carriage return <@optimize> tells the server to compact the witango code to remove the [default|specified] characters. This indicates that the specified characters are included only for readability, and do not need to be included in the ResultsHTML. This tag has no effect on the Results of metags, as it is applied before the code is executed. Bill ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
