[OASIS Issue Tracker] Updated: (ODATA-289) Callback for notification after 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:all-tabpanel ]

Hubert Heijkers updated ODATA-289:
----------------------------------

         Proposal: 
Introduce a new prefer header named 'odata.callback' which can be used in combination with either the respond-async or odata.track-changes preferences. The following is the text proposed to be added to the protocol document:

There are two scenarios in which links are being returned which are then later used to retrieve information, following a previous request, from the server. These are:
•	The service has provided a Location header pointing to a status monitor resource, in a response to a request which specified the respond-async preference in the prefer header.
•	The service has provided a delta-link in a response to a request in which the client expressed his desire to be able to track subsequent changes, by specifying the odata.track-changes preference in the prefer header.

To prevent having to poll the server for updates, not knowing if any information is available, the client MAY specify the odata.callback preference requesting the service to notify the consumer when data has become available.

The odata.callback preference MUST specify a URL to a service endpoint, using a parameter named 'url', that the service will invoke to notify the consumer. If the URL specifies an HTTP endpoint, the service will execute a HTTP GET request against the specified URL to notify the consumer. A service may support other, non HTTP, service endpoints should be advertised using a capability annotation. 

The odata.callback preference only has meaning when used in combination with the respond-async and odata.track-changes preferences.

If the service honors the odata.callback preference it MUST include odata.callback in the Preference-Applied response header.


  was:Can there be header or URL parameter to give indication to the service provider that request is asynchronous and response will be collected later

      Environment: [Proposed]
    Fix Version/s: V4.0_CSD02

> Callback for notification after 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
>         Environment: [Proposed]
>            Reporter: Ramanjaneyulu Malisetti 
>             Fix For: V4.0_CSD02
>
>
> 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