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] (ODATA-809) Define non-message format for final response of async request

    [ https://issues.oasis-open.org/browse/ODATA-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59846#comment-59846 ] 

Michael Pizzo commented on ODATA-809:

From discussion 2015-6-18:
Proposal is:
-If client does not specify application/http, but does specify application/json, the final results are not wrapped.
-Add a new header, such as "OData-AsyncResult", whose value is the result code of the asynchronous operation and whose presence signals that the response has completed and the payload and headers represent the outcome of the asynchronous request. Services would always return this header value on the final result (whether wrapped or not).

> Define non-message format for final response of async request
> -------------------------------------------------------------
>                 Key: ODATA-809
>                 URL: https://issues.oasis-open.org/browse/ODATA-809
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.1_WD01
> Today we define that, once an async result completes, polling the previously returned location header returns an HTTP-Message response that wraps the response (status, headers and body) that would have been returned if the request had processed synchronously:
> "A GET request to the status monitor resource returns 200 OK once the asynchronous processing has completed. This response MUST include a Content-Type header with value application/http and a Content-Transfer-Encoding header with value binary as described in [HTTP-Message]. The response body MUST enclose a single HTTP response which is the response to the initial Data Service Request."
> We did this in order to distinguish between the case that the request for status returned an error and the case where the response to the initial asynchronously request was an error.
> Everyone understands this once explained to them, but nobody likes it.

This message was sent by Atlassian JIRA

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