[OASIS Issue Tracker] (ODATA-809) Define non-message format for final response of async request

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

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

Ralf Handl updated ODATA-809:
-----------------------------

    Labels: AdoptionBlocker  (was: )

> 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
(v6.2.2#6258)