Insufficient Granularity in READ Operations

XMLWordPrintable

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

      I propose that READALL be modified such that it is type-specific. The fields in the request would be: 'type' => The type being queried; 'name' => omitted or null.

      DISCOVER-NAMES should be changed in the same way such that it returns only the names of entities in the specified type.

      Show
      I propose that READALL be modified such that it is type-specific. The fields in the request would be: 'type' => The type being queried; 'name' => omitted or null. DISCOVER-NAMES should be changed in the same way such that it returns only the names of entities in the specified type.

      There are two ways of reading manageable entities in this specification: READ and READALL. The READ operation accesses a single entity and the READALL operation accesses all of the entities.

      It would be practical to have a way to access all of the entities of a particular type. This is a very common use case in management scenarios. Furthermore, READALL is likely to involve a very large number of entities in any realistic situation.

      As an implementer, I would prefer to use operations that fetch data about entities of a particular type (either the whole table or just the names).

      Please note that this issue is related to AMQP-88.

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

              Created:
              Updated: