[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 ]

Ralf Handl updated ODATA-31:
----------------------------

    Proposal: 
Follow Martin's presentation "[Choreography for Asynchrones Requests](https://www.oasis-open.org/committees/download.php/48081/AsyncODataProposal.ppt)" in the January F2F

Accepted: https://www.oasis-open.org/committees/download.php/48097/odata-meeting-23_on-20130130_31-F2F-minutes.html#odata-31

  was:Follow Martin's presentation "[Choreography for Asynchrones Requests](https://www.oasis-open.org/committees/download.php/48081/AsyncODataProposal.ppt)" in the January F2F


> 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 v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: 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