You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Ben O'Day (JIRA)" <ji...@apache.org> on 2011/03/30 06:54:05 UTC

[jira] [Updated] (CAMEL-1669) Throttler - Should be more dynamic and be able to throttle per message correlation

     [ https://issues.apache.org/jira/browse/CAMEL-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben O'Day updated CAMEL-1669:
-----------------------------

    Attachment: CAMEL-1669.patch

here is an updated patch that adds expression support to throttler.  should provide the needed flexibility to address this issue... 

> Throttler - Should be more dynamic and be able to throttle per message correlation
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-1669
>                 URL: https://issues.apache.org/jira/browse/CAMEL-1669
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Ben O'Day
>             Fix For: Future
>
>         Attachments: CAMEL-1669.patch
>
>
> The throttler in Camel is a bit to static. Its only accepts numeric values to configure it.
> And it throttle the same for all messages going through it.
> What is needed to let it be more dynamic is:
> - configuration using expression
> - dynamic configuration at runtime, eg passing in new values in a message header
> - notion of grouping by using a correlation expression so you can have different QoS for different message groups
> ** eg gold, silver and bronze
> See nabble:
> http://camel.465427.n5.nabble.com/Suggestions-on-setting-different-Throttler-values-per-Client-td474883.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira