[
https://issues.apache.org/jira/browse/CAMEL-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020597#comment-13020597
]
Claus Ibsen commented on CAMEL-1669:
------------------------------------
The only feature which we don't support is correlated message groups. That
requires a bit more work and also may complicated the configuration a bit as
you would need to configure
- expression to evaluate the correlation key
And then the throttler logic need to have a map of correlation key -> TimeSlot
> 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: 2.8.0
>
> Attachments: CAMEL-1669.patch, 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
