Notes

A comment tag can appear anywhere in a server response file-even before the Handler tag.
If a comment tag is immediately followed by the end-of-line character, the newline character is removed with the comment tag. This is useful when placing tags into a file where white space is significant. For example, a server response file could be coded like this:
```
{{//There must be no whitespace rendered before the exchange tag, }}
{{// hence the newline-eating comment tags }}
{{ Handler * }}
{{ Trace(start,queryparam=trace,ip=127.0.0.1) }}
{{ SetEnv(A_CONFIG=../common/cblconfig.txt) }}
{{ ServiceLibs(xmlif) }}

{{ StartService(webappsample2.acu) }}
{{ XMLExchange(OnExit="gotit.srf") }}
```
Here, the Handler, Trace, SetEnv, ServiceLibs, and StartService tags are completely removed from the output, while the XMLExchange tag is replaced by the XML produced by the COBOL program. However, the new line character that follows each of these tags would remain in the output, resulting in four blank lines before the start of the XML produced by the XMLExchange tag.

To avoid this in this sample, the non-comment Handler, SetEnv, ServiceLibs, and StartService tags are followed by empty comments, which suppress the newline characters. The XMLExchange tag is not followed by a newline-consuming comment because a newline is desirable before the end of the file and, in this case, the emitted XML does not contain any newline characters.
```
{{//There must be no whitespace rendered before the exchange tag, }}
{{// hence the newline-eating comment tags }}
{{ Handler * }}{{//}}
{{ Trace(start,queryparam=trace,ip=127.0.0.1) }}{{//}}
{{ SetEnv(A_CONFIG=../common/cblconfig.txt) }}{{//}}
{{ ServiceLibs(xmlif) }}{{//}}

{{ StartService(webappsample2.acu) }}{{//}}
{{ XMLExchange(OnExit="gotit.srf") }}
```
Here, the comment tags and the Handler, Trace, SetEnv, ServiceLibs, and StartService tags are completely removed from the output, while the XMLExchange tag is replaced by the XML produced by the COBOL program.