[
https://issues.apache.org/jira/browse/OLINGO-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130394#comment-15130394
]
Dirk Mahler commented on OLINGO-858:
------------------------------------
Interesting: I ran into the same issue some days ago on a customer project :-)
I've created a local patch here to support streams in Olingo V2 for Atom feeds
- it works well but our use case is quite limited so far. The basic idea is to
replace the CircleStreamBuffer in AtomEntityProvider with an OutputStream
implementation that may provide chunks which are consumed by reading from the
InputStream which is later-on copied to the ServletOutputStream.
I'm going to clarify IP stuff here to see if we can create a patch out of it.
> 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)
