You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/02/19 09:28:12 UTC

[jira] [Updated] (CAMEL-8368) Timer component - Support for greedy, backoff

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

Claus Ibsen updated CAMEL-8368:
-------------------------------
    Fix Version/s:     (was: Future)

> Timer component - Support for greedy, backoff
> ---------------------------------------------
>
>                 Key: CAMEL-8368
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8368
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.15.0
>
>
> Look into letting timer endpoint support those backoff, greedy options we have. The idea would be that the exchange at the end of the routing, has some property/header, that the timer consumer understands, and then know if it should regard as one message polled, or zero message polled, etc.
> Then greedy, backoff, and the other options can work as usual.
> This allows people to have the simple timer scheduler to scale up / down depending on demand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)