[OASIS Issue Tracker] (ODATA-1046) Add JSON format for Batch

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

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

Ralf Handl commented on ODATA-1046:
-----------------------------------

Responding to a multipart batch request with a JSON batch response will be tricky as the JSON response uses named "groups" instead of unnamed change sets and has no implicit ordering, so it will be hard to correlate responses to requests if the requests don't specify a content-id, which we only require within change sets, not within top-level requests.

Same the other way round: the JSON batch request provides group names that cannot be represented in a multipart batch response, and it also doesn't require (in the current proposal) to have "id" members on all requests. If the groups don't specify a "dependsOn", no unique order of the individual requests can be established to determine the sequence of individual responses in the multipart batch response.

> Add JSON format for Batch
> -------------------------
>
>                 Key: ODATA-1046
>                 URL: https://issues.oasis-open.org/browse/ODATA-1046
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: JSON Format, Protocol
>    Affects Versions: V4.01_WD01
>         Environment: Applied with lots of questions
>            Reporter: Michael Pizzo
>             Fix For: V4.01_CSD02
>
>
> Our batch request and response format today is multipart/mime.  We've had a lot of pushback from the beginning that this format is difficult to construct and parse; there are no off-the shelf tools or libraries for doing so.
> Now that we have a JSON format for CSDL, a JSON client no longer needs an XML parser to read CSDL, but they still have no way of expressing or consuming a batch without parsing the difficult to understand/complex multi-part mime.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)