3.5.2 Data Display Conventions
The typical (server behavior only) example shows an initial state, a request, a response, and a final state.
The initial and final states highlight the changes for methods that perform updates. If the method is a query, then only the initial state is shown.
States are rendered using the LDP tool. The LDP transcript shown has been edited slightly for clarity. Specifically:
The "ld" and "&msg" are not shown for each search request. Nor is the "0" that means "typesOnly = false".
The actual attribute list is shown, in italics, within square brackets. The LDP tool does not show it in the transcript it produces.
The numeric constant that controls the search scope is replaced by its [RFC2251] name: baseObject, singleLevel, or wholeSubtree.
For example, the string:
ldap_search_s(ld, "DC=CONTOSO,DC=COM", 0, "(objectclass=*)", attrList, 0, &msg)
in the LDP transcript is changed to:
ldap_search_s("DC=CONTOSO,DC=COM", baseObject, "(objectclass=*)", [repsTo])
assuming that the search requested that only the repsTo attribute be returned.
Requests and responses are rendered by using the Windows debugger in the context of the server (for server behavior) or client (for client behavior), with editing of the transcript for clarity. The following two edits are performed consistently:
The DRS_HANDLE parameter is not shown.
Where the value of a parameter is a binary large object (BLOB), the value is not shown, but instead expressed as binary blob.