[ https://issues.apache.org/jira/browse/CAMEL-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben O'Day updated CAMEL-1669: ----------------------------- Description: 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 was: 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://www.nabble.com/Suggestions-on-setting-different-Throttler-values-per-Client-td23868691s22882.html > 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 > > > 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. - You can reply to this email to add a comment to the issue online.