[OASIS Issue Tracker] (ODATA-868) Describe HTTP encoding for streamed requests and responses

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

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

Michael Pizzo commented on ODATA-868:
-------------------------------------

My assumption is that a JSON response is always valid JSON. It may contain a next link if it contains collections, and nested collections may contain next links, but the overall response should be a valid JSON document.

The question here is what to do if a single JSON object can't be returned in a single response (i.e., there are too many properties in the object).

I would like to confirm the first assertion and consider the question as to what to do if the single JSON object can't be returned.

> Describe HTTP encoding for streamed requests and responses
> ----------------------------------------------------------
>
>                 Key: ODATA-868
>                 URL: https://issues.oasis-open.org/browse/ODATA-868
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA02
>         Environment: CSD02
>            Reporter: Ralf Handl
>              Labels: Clarification
>             Fix For: V4.01_WD01
>
>
> OData JSON Format has a format parameter for streaming scenarios but does not describe how these messages should be encoded.
> Part 1: Protocol, section 9.4 talks about in-stream errors in a format-independent way. Unfortunately we don't define how these should be represented in the JSON format.
> Situations where in-stream errors can occur include
> - metadata requests in XML or JSON
> - data request in JSON or XML
> - media resource requests with any content-type



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