Re: [provision] Non-batchable operations.

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

I agree that this is the real question, so I'll repeat the original 
content (since it may have been lost or buried in subsequent replies in 
this thread).

It seems clear to me that:
1) 'listTargets' is not batchable
   (for the same "bootstrapping" reasons that it is synchronous).
2) 'batch' is not batchable
   (it would be a mess to nest these).
3) 'search' is not batchable
   (the batch response could become far too large).
4) 'iterate' is not batchable
   (for the same reasons that it must be synchronous)

I don't see why Async Capability operations would be batchable
(since they must be synchronous and batch is usually async):
5) 'cancel' should not be batchable
   (seems weird to batch a cancel request with other requests;
    the batch would have to be synchronous)
6) 'status' should not be batchable
   (seems weird to batch a status request with other requests;
    the batch would have to be synchronous)

Finally, I'm not sure that Bulk Capability operations should be batchable
(but I cannot really say that this would cause a problem):
7) 'bulkModify' ?
8) 'bulkDelete' ?

Everything else (add, lookup, modify, delete, setPassword, 
expirePassword, resetPassword, validatePassword) seems okay to be 
batchable.

I lean toward normatively specifying at least those that are NOT 
batchable. For example, to batch a listTargets request is a logical 
error.  To batch a batch request seems a very bad idea--this way lies 
madness.

Jeff Bohren wrote:

>So now the real question is what should normatively specified as batchable. I really don't see any value in normatively calling out certain verbs and declaring them batchable. I would lean towards leaving this unspecified.
> 
>