Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: No Action
    • Affects Version/s: 5
    • Fix Version/s: 5
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      Removing the id/value pairs length field and instead having an "end of id value pairs" indicator, or reserve an id/value pair type number for the payload and mandate that this is the last id/value pair.

      Show
      Removing the id/value pairs length field and instead having an "end of id value pairs" indicator, or reserve an id/value pair type number for the payload and mandate that this is the last id/value pair.
    • Resolution:
      Hide

      Reviewed on 12/15 TC call and agreed to close and NOT revisit the earlier design consensus that Ken noted in his comments.

      Show
      Reviewed on 12/15 TC call and agreed to close and NOT revisit the earlier design consensus that Ken noted in his comments.

      Description

      The current spec requires an id/value pair length field indicating how many bytes constitute the id/value pairs in the controlpacket, prior to any payload that may be in the controlpacket as well. From an implementer's point of view this means allocating and building a buffer to hold this data so it can be counted and the value inserted logically prior to this buffer. This is particularly problematic as the value is a Variable Byte Integer so space in a larger control packet buffer cannot be preallocated then filled afterwards (same annoyance occurs with the remaining length field earlier in the control packet).

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              al.s-m Allan Stockdill-Mander
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: