OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

amqp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: AMQP Management Operations


I've replied one technical point on the OASIS list:

https://lists.oasis-open.org/archives/amqp/201307/msg00011.html

In general I am also in favour of being able to add restrictions to the READALL and DISCOVER-NAMES operations such that the only bring back objects of a given type.

-- Rob


On 30 July 2013 22:55, Ted Ross <tross@redhat.com> wrote:
In reference to the AMQP Management Spec. v1.0 (wd02):

I see that for retrieving information about manageable objects in a container there are a few options:

 * Use the "READ" operation to query a specific object by name,
 * Use the "READALL" operation to query every object in the container,
 * Use the "DISCOVER-NAMES" operation to get the names of all objects
   and then "READ" to query individual objects.

I can envision situations where a given container may contain very large numbers of objects (possibly millions).  In this case, READALL and DISCOVER-NAMES will be impractical to use (i.e. they will return with "413 - Request entity Too Large").  Using the optional "limit" argument doesn't appear to help.  The thing I'm looking for may be beyond the limit and I'll never see it.

It would be good to have a way to query all objects of a particular type.  Can READALL and DISCOVER-NAMES be altered such that specific type names can be used, rather than only allowing "org.amqp.management"?

Thanks,

-Ted




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]