Re: [provision] Batch Capability.

[Gary P Cole <Gary.P.Cole@Sun.COM>]

Having heard no objection, I assume that the list agrees to define the 
'batch' operation as part of a Batch capability (which means that the 
batch operation becomes optional).

gpc

Gary P Cole wrote:

> Should 'batch' be a required operation?
> Right now 'batch' is part of the core (which de facto makes it 
> required), but it doesn't really have to be part of the core.  It's 
> not a *basic* operation (like 'add', 'modify', 'delete', or 'lookup') 
> and it's not a *bootstrap* operation (like 'listTargets').  It's an 
> operation that wraps multiple (batchable) requests in a single request.
>
> I think we should move the 'batch' operation to a Batch Capability 
> (for the same reasons that we moved 'search' to the Search 
> Capability).  The 'batch' operation imposes a fair amount of 
> complexity on the provider, and should be optional.1) The 'batch' 
> operation requires that the provider order nested results within its 
> response (to correspond with the order of the requests within the 
> original request).
> 2) The batch operation also also allows the requestor to specify 
> "processingType" as either "sequential" or "parallel".