Uploaded image for project: 'OASIS Advanced Message Queuing Protocol (AMQP) TC'
  1. OASIS Advanced Message Queuing Protocol (AMQP) TC
  2. AMQP-91

Entity operations use name to identify the entity ... should the name be unique?

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: WD02
    • Fix Version/s: None
    • Component/s: Management
    • Labels:
      None

      Description

      The chapter 2.4.1 defines that every manageable entity should have a name (which is just a label) and the identity (which is an unique immutable identity name). The entity operations - e.g. UPDATE or DELETE - are using the name to identify the entity on which the operation should be done. However, unlike the identity, the entity name has no requirement to be unique. Therefore, in situations when several entities have the same name and type, it is not clear what would be the expected result.

      Shouldn't the specification require the name to be unique within the management node? Especially, since the already unique identity cannot be used in any request.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              scholzj Jakub Scholz (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: