Re: [provision] Issue 16, cancel results...

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

Does Draft 9 contain your proposed changes to remove sync/async from the 
core?  If not, then I think we should go ahead and remove cancelResult 
from CancelResponseType and remove CancelResultsType. (After all, it's 
easy enough to add it back once you've made your proposal and it's been 
accepted.)

The current understanding on the list is that a provider either cancels 
the requested operation or returns an error.

Jeff Bohren wrote:

> Issue 16 reads
>
>  
>
> 16.    Don't need CancelResultsType; ResultCode and ErrorCode
>
> should suffice
>
>  
>
> If we are going to have asynchronous requests as capability, I would 
> like to move farther towards removing all notion of sync/async from 
> the core. I have a solution for this that I would like to propose, but 
> it does result in there still being a CancelResultsType defined in the 
> async capability.
>
>  
>
> Jeff Bohren
>
> Product Architect
>
> OpenNetwork Technologies, Inc
>
>  
>
> Try the industry's only 100% .NET-enabled identity management 
> software. Download your free copy of Universal IdP Standard Edition 
> today. Go to www.opennetwork.com/eval <http://www.opennetwork.com/eval>.
>
>  
>
>  
>
>  
>