OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Anila Kumar GVN commented on ODATA-289:

We supported asynchronous notifications from our OData services based on pubsubhubbub protocol.

When a callback URL is provided by the client during a call, the service (hub) verifies the intent of the client by challenging the callback URL. On successful response form the client for the challenge, the server assumes the callback URL is indeed client's URL and it can send async notifications to that URL (ofcourse on successful authorization of the subject against response payload).

And the notifications are again OData format. (i.e., the callback is an OData service!)

If OData can speciify a similar protocol as part of the spec, then it should enable OData producers and consumers to share a standardized asynchronous callback and notification mechanism.

> 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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]