[jira] [Commented] (CAMEL-6476) StreamCachingStrategy - A better strategy

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690247#comment-13690247 ] 

Claus Ibsen commented on CAMEL-6476:
------------------------------------

For streams with no mark support, we could maybe do a copy on-demand, so when we reset, we can read from the copy, and if we didn't read it all, we just switch over to the original stream at point of break. 
                
> StreamCachingStrategy - A better strategy
> -----------------------------------------
>
>                 Key: CAMEL-6476
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6476
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.12.0
>
>
> The old stream caching has some flaws such as
> - copying the existing stream into an internal buffer/type
> - spool to disk by default
> - a bit confusing to configure
> - wrap based
> - not exposed in JMX
> - not easy to implement custom strategies
> Working on a new strategy that supports
> - reusing existing stream if it supports marks
> - memory based only by default
> - threshold for spooling to disk based on memory usage, and payload sizes
> - use the internal camel processor to avoid wrapping
> - exposed in JMX with runtime stats
> - only enabled if explicit turned on
> - log at INFO level on startup if enabled and what settings is in use
> - configuring in the DSL with a xxxDefinition to make it stand out in the XML DSLs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira