[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-31) Section 9.1.3: Describe call choreography for 202 Accepted (Async responses)
[ http://tools.oasis-open.org/issues/browse/ODATA-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Drees updated ODATA-31:
------------------------------
Resolution:
I applied the proposal to the spec as described in the presentation with one deviation: In the presentation the async response was enclosed in an HTTP response with content -type message/http, I changed that to the content-type application/http with content-Transfer-Encoding binary for two reasons:
1. For message/http exists restrictions regarding line length and encodings.
2. Consistency with the OData batch format. In batch we use for the exactly same purpose (enclosing a singe HTTP response in a
HTTP envelope) the content-typeheader with value application/http and a Content-Transfer-Encoding header with value binary.
https://www.oasis-open.org/committees/download.php/48604/odata-core-v4.0-wd01-part1-protocol-2013-03-20.doc
Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-31
was:
I applied the proposal to the spec as described in the presentation with one deviation: In the presentation the async response was enclosed in an HTTP response with content -type message/http, I changed that to the content-type application/http with content-Transfer-Encoding binary for two reasons:
1. For message/http exists restrictions regarding line length and encodings.
2. Consistency with the OData batch format. In batch we use for the exactly same purpose (enclosing a singe HTTP response in a HTTP envelope) the content-typeheader with value application/http and a Content-Transfer-Encoding header with value binary.
https://www.oasis-open.org/committees/download.php/48604/odata-core-v4.0-wd01-part1-protocol-2013-03-20.doc
> Section 9.1.3: Describe call choreography for 202 Accepted (Async responses)
> ----------------------------------------------------------------------------
>
> Key: ODATA-31
> URL: http://tools.oasis-open.org/issues/browse/ODATA-31
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData Protocol
> Affects Versions: V4.0_WD01
> Environment: [Proposed]
> Reporter: Ralf Handl
> Assignee: Martin Zurmuehl
> Fix For: V4.0_WD01
>
>
> Describe choreography, i.e.
> - POST/PUT/PATCH: 202
> - *(GET Loc: 202)
> - GET Loc: 303
> - GET Loc: 200/201/204/4xx/5xx
> Example: update media resource triggers virus scan in server, may take some time, may succeed (204), detect a virus (4xx), or crash (5xx)
--
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]