[
https://issues.apache.org/jira/browse/OLINGO-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitko Kolev updated OLINGO-858:
-------------------------------
Description:
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. The loading
of the stream in memory is extremely painful when the entity stream is huge.
was:
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. The loading
of the stream in memory is extremely painful when the entity does not fit in
memory.
> 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
>
> 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. The loading
> of the stream in memory is extremely painful when the entity stream is huge.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
