[
https://issues.apache.org/jira/browse/OLINGO-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-858.
------------------------------------
Resolution: Won't Fix
Assignee: Christian Amend
Hi Mitko,
unfortunately in V2 of OData and especially with the current Olingo V2
architecture streaming is not possible.
OData V2 makes this especially hard because you have to send a specific and
enclosed error message if a request failed. This is impossible if you have
already started streaming content to a client.
So for now we don`t plan to provide this feature. If you have a contribution
you would like to make please let me know and we can discuss this.
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: Christian Amend
>
> 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)
