[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (AMQP-91) Entity operations use name to identify the entity ... should the name be unique?
Entity operations use name to identify the entity ... should the name be unique?
--------------------------------------------------------------------------------
Key: AMQP-91
URL: http://tools.oasis-open.org/issues/browse/AMQP-91
Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
Issue Type: Improvement
Components: Management/Monitoring
Affects Versions: WD02
Reporter: Jakub Scholz
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]