[
https://issues.apache.org/jira/browse/CAMEL-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522069#comment-16522069
]
ASF GitHub Bot commented on CAMEL-6840:
---------------------------------------
davsclaus commented on issue #2376: CAMEL-6840 - add grouped throttling
feature, both XML and Java DSL should be fine now.
URL: https://github.com/apache/camel/pull/2376#issuecomment-399886312
This PR is a bit hard to grok - especially that code that does that
completion future task. For me it looks like you use a thread pool to do some
work to find a delay queue, and then do a future get to block and wait for that
thread to finish. What is the reason for that?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Allow Throttler EIP to specify SLA per client/correlated-group
> --------------------------------------------------------------
>
> Key: CAMEL-6840
> URL: https://issues.apache.org/jira/browse/CAMEL-6840
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
> Reporter: Christian Posta
> Assignee: Önder Sezgin
> Priority: Major
> Fix For: 2.22.0
>
>
> Basic idea is to allow throttler to have a predicate to determine whether or
> not to apply throttling to that exchange.
> From this Mailing List discussion:
> http://camel.465427.n5.nabble.com/Throttling-by-client-ID-td5741032.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
