[
https://issues.apache.org/jira/browse/OLINGO-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130558#comment-15130558
]
Christian Amend commented on OLINGO-858:
----------------------------------------
Hi Dirk,
this sounds interesting. If you can share some information I would also be
interested how you handled errors while streaming. Specifically which error
format you used and how the client reacted to them. Since there is nothing in
the specifcation about these in-stream errors the client must have had some
costem coding as well right?
Best Regards,
Christian
> org.apache.olingo.odata2.api.processor.ODataResponse enity is not streamed
> --------------------------------------------------------------------------
>
> Key: OLINGO-858
> URL: https://issues.apache.org/jira/browse/OLINGO-858
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
> Affects Versions: V2 2.0.5
> Reporter: Mitko Kolev
> Assignee: Michael Bolz
>
> The entity of the {{org.apache.olingo.odata2.api.processor.ODataResponse}} is
> not streamed.
> {code}
> ODataResponse.newBuilder().entity(someInputStream).header("Content-Type",
> "application/octet-stream")
> .status(HttpStatusCodes.OK).build()
> {code}
> It would make sense to stream this directly in the HTTP response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
