kmip-interop-tech — archive

[John Leiseboer]

Hi Dave, Your batch example is flawed. A batch set of operations is a convenient means of requesting the server to perform several operations specified in a single request message. Your example is functionally equivalent to a client sending two separate requests, {Create w/template} followed later by {Add/x-ID}. This results in the Add/x-ID instance getting index 2, just as the batch request would. (I have taken the liberty of assuming that batch order option is set, otherwise the result of the batch request could actually be an error - adding an attribute to an object not yet created would be difficult to achieve :-) Note that option 2 provides the client with more flexibilty. Depending on which index order the client wants, it can choose which method to use; i.e. it can choose to accept the ordering provided by the Template, or override it by including x-ID in the create with template. Without this flexibilty,  the x-ID attribute index in the template would always take priority over the attribute in the request - exactly the opposite priority of "ordering" for single-instance attributes! John Sent from my Samsung Galaxy Note 4 on the Telstra Mobile network