Response records
Each data interface response contains a single header record followed by zero or more data records.
If the response contains multiple records, each record is separated from the next by a new-line sequence. For an illustration of the structure of an HTTP response from a data interface request, see Figure 1.
Your client application encodes data interface command options using standard URL-encoding, and the Web User Interface server uses the same techniques for response records. For example, two record fields and their values are expressed as follows:
field1=value1&field2=value2
You encode special characters in field names and values (including space, &, and =) using escape characters that follow the escaping scheme described in the URL specification. The URL escaping scheme specifies that escaped characters are represented by a % (percent sign) followed by 2 hexadecimal digits (in ASCII code). (For information about encoded strings, where some characters can be escaped using "% HEX HEX" see the Uniform Resource Locators (URL) memorandum, RFC1738, at www.ietf.org/rfc/.)
The data interface encodes all data flows in the ISO-8859–1 code page, using the Web User Interface ENU1 conversion table and follows a standard character representation, regardless of the Web User Interface server's current language or locale settings. You do not need to ensure that the client is using same language and code page as the server. However, your client application might have to convert some character representations used by the data interface to those required by the client application; for example, if you want to use different separator characters for time and date fields.