[
https://issues.apache.org/jira/browse/OLINGO-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144303#comment-15144303
]
Mitko Kolev commented on OLINGO-858:
------------------------------------
Hi Michael,
{quote}
The default {{Producer}} implementations in Olingo are not supporting streaming
of the serialized content.
But if e.g. a MediaEntity and the {{EntityMediaProcessor}} is used streaming
can be provided by the service.
{quote}
I think supporting streaming in the {{EntityMediaProcessor}} should be the very
first step. The streaming in the read entity set processor should not be that
critical, because it can be nicely worked around by introducing paging.
However, processing a streaming input in the batch processor seems to be a big
challenge with the current architecture.
I will think of a contribution for the {{EntityMediaProcessor}} if I find time
in the near future.
Best regards,
Mitko
> 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)
