[OASIS Issue Tracker] Commented: (ODATA-289) Async invocation of Create, Update, Delete and Service Operations

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32824#action_32824 ] 

Ralf Handl commented on ODATA-289:
----------------------------------

Independent of the authentication problem a service probably doesn't want to send the actual response to the callback address, but instead send a poke notification that triggers the client to pull the asynchronous response using the address in the location header of the initial 202 Accepted response of the service. That way the service can make sure that it is actually talking to the same client, or a client that is authorized to see the response.

> Async invocation of Create, Update, Delete and Service Operations
> -----------------------------------------------------------------
>
>                 Key: ODATA-289
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-289
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions 
>    Affects Versions: V4.0_WD01
>            Reporter: Ramanjaneyulu Malisetti 
>
> URL convention for Create and Update implicitly assumes that clients make synchronous invocation. However, some data sources may take longer time to fulfill the request and hence suggest clients to make asynchronous invocation of these operations and response will be available at specific URL.
> Similar mechanism for service operations as well

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira