BIND 10 trac2671, updated. 5d3ce61a456ae34baf4d16ed5eab7eb2b22251b3 [2671] Types for the headers

[BIND 10 source code commits]

The branch, trac2671 has been updated
       via  5d3ce61a456ae34baf4d16ed5eab7eb2b22251b3 (commit)
       via  efc0544bdf19f781e928c4cc6f764439ebc5e414 (commit)
      from  20f4fc2b067a6c4969cfded667e6a0d7ad90e1dc (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 5d3ce61a456ae34baf4d16ed5eab7eb2b22251b3
Author: Michal 'vorner' Vaner <michal.vaner at nic.cz>
Date:   Tue Mar 5 09:46:59 2013 +0100

    [2671] Types for the headers

commit efc0544bdf19f781e928c4cc6f764439ebc5e414
Author: Michal 'vorner' Vaner <michal.vaner at nic.cz>
Date:   Tue Mar 5 09:41:44 2013 +0100

    [2671] More political comment about instance

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

Summary of changes:
 doc/design/cc-protocol.txt |   31 ++++++++++++++++---------------
 1 file changed, 16 insertions(+), 15 deletions(-)

-----------------------------------------------------------------------
diff --git a/doc/design/cc-protocol.txt b/doc/design/cc-protocol.txt
index 12c5c57..15db9c1 100644
--- a/doc/design/cc-protocol.txt
+++ b/doc/design/cc-protocol.txt
@@ -13,9 +13,10 @@ sender.
 
 A client may subscribe to a group of communication. A message can be
 broadcasted to a whole group instead of a single client. There's also
-an instance parameter to addressing, but its only obvious purpose is
-to clutter the code, since the original intention is not remembered by
-anyone and it is left at the default `*` in all cases.
+an instance parameter to addressing, but we didn't find any actual use
+for it and it is not used for anything. It is left in the default `*`
+for most of our code and should be done so in any new code. It wasn't
+priority to remove it yet.
 
 Wire format
 -----------
@@ -52,18 +53,18 @@ The headers
 
 The header object can contain following information:
 
-|============================================================================
-|Name       |Description
-|============================================================================
-|from       |Sender's l-name
-|type       |Type of the message. The routed message is "send".
-|group      |The group to deliver to.
-|instance   |Instance in the group. Purpose lost in history. Defaults to "*".
-|to         |Override recipient (group/instance ignored).
-|seq        |Tracking number of the message.
-|reply      |If present, contains a seq number of message this is a reply to.
-|want_answer|If present and true, the daemon generates error if there's no matching recipient.
-|============================================================================
+|====================================================================================================
+|Name       |type  |Description
+|====================================================================================================
+|from       |string|Sender's l-name
+|type       |string|Type of the message. The routed message is "send".
+|group      |string|The group to deliver to.
+|instance   |string|Instance in the group. Purpose lost in history. Defaults to "*".
+|to         |string|Override recipient (group/instance ignored).
+|seq        |int   |Tracking number of the message.
+|reply      |int   |If present, contains a seq number of message this is a reply to.
+|want_answer|bool  |If present and true, the daemon generates error if there's no matching recipient.
+|====================================================================================================
 
 Types of messages
 -----------------