BIND 10 trac2230, updated. 750f6fecbe3e5e8b74a309679b129e35895fc841 [2230] Comments on byte order and endianess in template files.

[BIND 10 source code commits]

The branch, trac2230 has been updated
       via  750f6fecbe3e5e8b74a309679b129e35895fc841 (commit)
      from  34238640001954f7fae9bdd69401b6b3bd5ad225 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 750f6fecbe3e5e8b74a309679b129e35895fc841
Author: Marcin Siodelski <marcin at isc.org>
Date:   Mon Sep 17 16:46:04 2012 +0200

    [2230] Comments on byte order and endianess in template files.

-----------------------------------------------------------------------

Summary of changes:
 tests/tools/dhcp-ubench/dhcp-perf-guide.xml |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

-----------------------------------------------------------------------
diff --git a/tests/tools/dhcp-ubench/dhcp-perf-guide.xml b/tests/tools/dhcp-ubench/dhcp-perf-guide.xml
index cbf1bf6..ac340b7 100644
--- a/tests/tools/dhcp-ubench/dhcp-perf-guide.xml
+++ b/tests/tools/dhcp-ubench/dhcp-perf-guide.xml
@@ -1024,7 +1024,10 @@ collected packets: 0
           dynamically (without the template). Note that each template file
           holds data for exactly one DHCP message type. Templates for multiple
           message types must not be combined in the single file.
-          The content in template files is encoded in hexadecimal format.
+          The content in template files is encoded as series of ASCII hexadecimal
+          digits (each byte represented by two ASCII chars 00..FF). Data in a
+          template file is laid in network byte order and it can be used on the
+          systems with different endianess.
           perfdhcp forms the packet by replacing parts of the message buffer read
           from the file with variable data such as elapsed time, hardware address, DUID
           etc. The offsets where such variable data is placed is specific to the