You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by richardgroote <ri...@gmail.com> on 2014/11/12 09:17:30 UTC
Why StreamResultHandlerFactory uses a byte[] instead of the stream
Hello,
The StreamResultHandlerFactory / StreamResultHandler sets a byte array in
the body.
Why not set the outputstream itself in the body then the processing is
streaming.
Kind regards,
Richard
PS Version of camel used is 2.12.2 (also checked the code of 2.14)
--
View this message in context: http://camel.465427.n5.nabble.com/Why-StreamResultHandlerFactory-uses-a-byte-instead-of-the-stream-tp5758961.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: Why StreamResultHandlerFactory uses a byte[] instead of the
stream
Posted by Willem Jiang <wi...@gmail.com>.
byte[] is rereadable and it’s easy for camel to turn it into an input stream.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On November 12, 2014 at 4:19:27 PM, richardgroote (richard.groote@gmail.com) wrote:
> Hello,
>
> The StreamResultHandlerFactory / StreamResultHandler sets a byte array in
> the body.
>
> Why not set the outputstream itself in the body then the processing is
> streaming.
>
> Kind regards,
>
> Richard
>
> PS Version of camel used is 2.12.2 (also checked the code of 2.14)
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Why-StreamResultHandlerFactory-uses-a-byte-instead-of-the-stream-tp5758961.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>