[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-868) Describe format for In-Stream errors
[ https://issues.oasis-open.org/browse/ODATA-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-868: ----------------------------- Description: In Part 1: Protocol, section 9.4 we talk 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 was:In Part 1: Protocol, section 9.4 we talk about in-stream errors in a format-independent way. Unfortunately we don't define how these should be represented in the JSON format. Proposal: No proposal yet, just a collection of ideas: - if error occurs, inject invalid character (sequence) in stream to stop parsing on client, then inject format-specific error body - streaming responses contain a header with a link to a monitor resource where clients can check whether the streamed response ended prematurely due to an error. - with HTTP/2 server can push response to monitor resource requests to client in case of errors - with HTTP/1.1 use chunked transfer encoding and send error information in trailing headers, e.g. an odata-error "header" that contains a header-friendly encoded JSON or XML error response > Describe format for In-Stream errors > ------------------------------------ > > 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 > Reporter: Ralf Handl > Labels: Clarification > Fix For: V4.01_WD01 > > > In Part 1: Protocol, section 9.4 we talk 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]