[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [amqp] Groups - AMQP Management v1.0 wd03 uploaded
Hi, Additionally to Ted's comments, I think there are some inconsistencies in the REGISTER/DEREGISTER/GET-MGMT-NODES operations. The GET-MGMT-NODES operation currently returns a list of addresses. However, the REGISTER and DEREGISTER operations work only with the nodeName application-property. So where do we get the address for the GET-MGMT-NODES? Is it expected that the address will be obtained from the link which sent the REGISTER request? Also, the GET-MGMT-NODES operation doesn't seem to return the nodeNames as promised in chapter 3.4.5.2. Thanks & Regards Jakub From: Ted Ross <tross@redhat.com> To: amqp@lists.oasis-open.org, Cc: Ted Ross <tross@redhat.com> Date: 17/01/2014 17:18 Subject: Re: [amqp] Groups - AMQP Management v1.0 wd03 uploaded Sent by: <amqp@lists.oasis-open.org> David, Thanks for the update. I have some questions/suggestions about the new QUERY operation. First, I'm a little confused by the fact that "Attributes" is mandatory and "entityTypes" is optional. To my understanding, attributes have type-specific meaning, so searching for common attributes over a set of types doesn't seem that useful to me. I would suggest that "entityTypes" be the mandatory property and "Attributes" be optional. "Attributes" is defined as a string, yet it is described as a "set". I think this property should be a list of strings where each item is an attribute name. If not supplied, all attributes of the returned entities should be included in the response. If supplied, only the listed attributes should be included. "entityTypes" is defined as a list which suggests that a response may contain entities of multiple types. This further suggests that the optional "type" attribute really isn't optional because without it, there would not be a way to determine the types of the entities in the response. I suggest that "entityTypes" be renamed "entityType", made mandatory, and changed to a string type. This means that all QUERY operations are on a single type. This allows the types of the entities in the response to be inferred as opposed to having to be individually identified. The "Count" property in the response is redundant with the count field of the list in the amqp-value body. It would be simpler to have a property of "maxCount" that doesn't carry any information back to the requestor. Depending on how the management agent is implemented, it might be onerous to encode the properties, then encode the body only to have to go back and re-encode one of the properties based on the size of the body. Regards, -Ted On 01/13/2014 06:49 PM, David Ingham wrote: Submitter's message A work-in-progress version with changes made to the core set of Manageable Entity Operations and Management Node Operations. -- Mr. David Ingham |--------------------------------------------------------------| |Document Name: AMQP Management v1.0 wd03 | |Description | |A work-in-progress version with changes made to the core set | |of Manageable | |Entity Operations and Management Node Operations. | |Download Latest Revision | |Public Download Link | |Submitter: Mr. David Ingham | |Group: OASIS Advanced Message Queuing Protocol (AMQP) TC | |Folder: Working Documents | |Date submitted: 2014-01-13 15:49:05 | | | |--------------------------------------------------------------| ---------------------------------------------------------------------------- Deutsche Börse Services s.r.o. Managing Directors/Geschäftsführung: Michael Gassmann, Mats Andersson. Limited liability company with registered office at Sokolovská 662/136B, CZ-186 00 Prague 8 recorded in the Commercial Register IC: 275 77 015. Maintained by the city court in Prague, Sec. C, File No. 116874. ----------------------------------------- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]