[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (AMQP-89) Insufficient Granularity in READ Operations
Insufficient Granularity in READ Operations ------------------------------------------- Key: AMQP-89 URL: http://tools.oasis-open.org/issues/browse/AMQP-89 Project: OASIS Advanced Message Queuing Protocol (AMQP) TC Issue Type: Improvement Components: Management/Monitoring Affects Versions: WD02 Reporter: Ted Ross 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. -- 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]