|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
ATL Server Response File Reference
Server response files consist of the following elements:
|Codepage Tag||A codepage tag can be added to a server response file to indicate the character set used in that file. Specifying the codepage allows the server response file to be parsed correctly if it contains characters that are not part of the ANSI character set.|
|Comment Tag||A comment tag allows you to add comments to the server response file that will be removed during processing.|
|Handler Tag||A handler tag identifies a request handler that will be used to render some or all of the replacement tags in that file.|
|Include Tag||An include tag can be added to a server response file to indicate the point at which the contents of another file should be included in the response.|
|Locale Tag||A locale tag can be added to a server response file to indicate the locale that should be used for any response generated from that point on in the file.|
|Replacement Tag||A replacement tag can be added to a server response file to indicate the point at which dynamic content should be inserted into a response. Replacement tags consist of two pairs of braces enclosing the name of a replacement method or a rendering instruction.|
|Subhandler Tag||A subhandler tag identifies a request handler that will be used to render some or all of the replacement tags in that file.|
|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.|
The elements of a server response file described in this section are those understood by the CHtmlStencil class. Further features can be added by deriving from this class and customizing the parsing code.
See the SRFSyntax Sample.