Inefficient Encoding of Manageable Entities

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: WD02
    • Component/s: Management
    • None
    • Hide

      One proposal for tightening up the encoding is to limit queries and responses to a singe type (I'll raise this as a separate issue). If this is done, then the type-name is implicitly known and the set of attributes (columns) is consistent across entities (rows).

      The encoding could then be a list of lists, the first list provides the attribute names (column headers) and the subsequent lists provide the values (rows).

      Show
      One proposal for tightening up the encoding is to limit queries and responses to a singe type (I'll raise this as a separate issue). If this is done, then the type-name is implicitly known and the set of attributes (columns) is consistent across entities (rows). The encoding could then be a list of lists, the first list provides the attribute names (column headers) and the subsequent lists provide the values (rows).

      In operations that return the contents of multiple manageable entities (READALL), the encoding of the data is very inefficient due to the repeated encoding of the same data:

      • Each entity has a 'type' attribute in its map. If there are N instances of a type, there will be N copies of the type name encoded.
      • For multiple instances of the same type, the type's attribute names (i.e. map keys) are redundantly encoded.

            Assignee:
            Unassigned
            Reporter:
            Ted Ross (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: