Skip to main content
ATL Server Library Reference 
Static Content 

Static content can be any text (most likely, but not limited to, HTML and XML) that doesn't clash with one of the parser's tags.

Server response files (SRF) can be used to generate HTML, XML, or any other text-based content type. However, the response file parser places a few restrictions on the static content of the SRF.

Double braces ("{{" and "}}") are given special consideration by the response file parser. When it encounters opening braces, the parser treats all text up to one character beyond the first closing brace as a single token. If no closing brace is found, an error is returned.

Content enclosed in double braces is interpreted as being one of the tags described in this reference. If, after parsing the contents of a pair of double braces, it turns out that the content does not exactly match one of these tags (for example, if the text looks like a replacement tag, but the request handler does not support the replacement method used), the whole tag is treated as static text and will appear unchanged in the response. This also applies to tags that are linked to these tags.

Note that line breaks ('\n' or '\r\n') immediately following the tags listed below are discarded and not added to the generated response:

It is unlikely that the static content you want to integrate into the rendered output will clash with the requirements imposed by the parser. However, if it does, you can put that content into a file that does not use the SRF extension and use the include tag to integrate the content into the response.

Note that UCS-4, UCS-2, and UTF-16 encoded SRFs are not supported. Multilingual responses can be generated using the UTF-8 encoding.