Re: [provision] Non-batchable operations.

[Darran Rolls <Darran.Rolls@Sun.COM>]

With many on the road this week, we should let this float on the list 
for a week before drawing a close. 

For my part, I agree with your assessment. 1-6 and say no to batchable 
bulks (now there's a mouth full :-)

One follow up question.  If one defines a new capability and one knows 
that it will be problematic to handle bulk and batch, is there a 
universal model for specifying "no batch" and "no bulk" on the capability?

Darran

Gary P Cole wrote:

> 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.
>
> In the interest of time (and to facilitate review), here's a list of 
> all operations.
>
> 3.4         Operations  22 <#_Toc90380484>
>
> 3.4.1                Core Operations  22 <#_Toc90380485>
>
> 3.4.1.1              listTargets  22 <#_Toc90380486>
>
> 3.4.1.2              add  28 <#_Toc90380487>
>
> 3.4.1.3              lookup  32 <#_Toc90380488>
>
> 3.4.1.4              modify  35 <#_Toc90380489>
>
> 3.4.1.5              delete  41 <#_Toc90380490>
>
> 3.4.2                Async Capability  43 <#_Toc90380491>
>
> 3.4.2.1              cancel 43 <#_Toc90380492>
>
> 3.4.2.2              status  45 <#_Toc90380493>
>
> 3.4.3                Batch Capability  50 <#_Toc90380494>
>
> 3.4.3.1              batch  50 <#_Toc90380495>
>
> 3.4.4                Bulk Capability  57 <#_Toc90380496>
>
> 3.4.4.1              bulkModify  57 <#_Toc90380497>
>
> 3.4.4.2              bulkDelete  59 <#_Toc90380498>
>
> 3.4.5                Password Capability  62 <#_Toc90380499>
>
> 3.4.5.1              setPassword  62 <#_Toc90380500>
>
> 3.4.5.2              expirePassword  64 <#_Toc90380501>
>
> 3.4.5.3              resetPassword  65 <#_Toc90380502>
>
> 3.4.5.4              validatePassword  67 <#_Toc90380503>
>
> 3.4.6                Reference Capability  70 <#_Toc90380504>
>
> 3.4.7                Search Capability  71 <#_Toc90380505>
>
> 3.4.7.1              search  71 <#_Toc90380506>
>
> 3.4.7.2              iterate  76 <#_Toc90380507>
>
> 3.4.8                Suspend Capability  80 <#_Toc90380508>
>
> 3.4.8.1              suspend  80 <#_Toc90380509>
>
> 3.4.8.2              resume  81 <#_Toc90380510>
>
> 3.4.8.3              active  83 <#_Toc90380511>
>
>
>
>
> To unsubscribe from this mailing list (and be removed from the roster 
> of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgroup.php. 
>
>