[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Further questions on Management wd04
David, Rob, Thanks again for the new working draft. I have some follow-on questions about the QUERY operation: My main concern is about the "entityTypes" key being optional and it being a list. This means that zero or more entityTypes can be involved in the query. This leads to a couple of difficulties:
I am satisfied with the text "...restricts the list of Manageable Entities requested to those that implement (directly or indirectly) the given Manageable Entity Type" from the description of "entityTypes". This means that, if given a single entityType, the agent will return the requested attributes from all entities of that type and of derived types (i.e. Query the names and depths of all types of queues). Having a list of entityTypes means I can ask for the names of all queues and links which is arguably meaningless, but I need to implement it anyway to be compliant. It's like a general-purpose JOIN query (without a selector). I think QUERY would be much simpler if "entityTypes" was made single (list => string) and was mandatory. Then there would be a way to interpret "all attributes" (when Attributes is omitted) and pagination would be scoped to a particular type (or sub-tree in the type hierarchy). -Ted |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]