[
https://issues.apache.org/jira/browse/OLINGO-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136301#comment-15136301
]
Michael Bolz commented on OLINGO-858:
-------------------------------------
Hi [~mkolev],
I have no concerns about some container/framework.
However, based on the used framework/environment there could be limitation
regarding to streaming.
E.g. the {{ODataResponse}} should not limit streaming, but used in combination
with the {{ODataServlet}} parts of the response are buffered before they get
handled by the {{ServletOutputStream}}. In combination with CXF and
{{ODataSubLocator}} this should not be the case.
{quote}
I just realized that supporting someInputStream would be OK, but even better
would be to have a callback to close the resources e.g. connection when the
work is done.
{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.
Best Regards,
Michael
> 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)
