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 2021/02/18 06:29:00 UTC

[jira] [Commented] (CAMEL-16222) camel-core - ExchangeFactory SPI

    [ https://issues.apache.org/jira/browse/CAMEL-16222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286300#comment-17286300 ] 

Claus Ibsen commented on CAMEL-16222:
-------------------------------------

After some experimentation I think we should focus this on

- consumers only
- use per consumer factory so there is no race condition if one global pool

There are other places in EIPs where sub exchanges are created (aggregator, splitter, wire tap) but it would complicate matters if they are also pooled.

By using per consumer we can also use that for back pressure where we can work on some  limits you can specify.
This requires some modest API addition to Consumer and to implement this across all the components, so the consumers in these components will use this new API instead of the classic.



> camel-core - ExchangeFactory SPI
> --------------------------------
>
>                 Key: CAMEL-16222
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16222
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.9.0
>
>
> It would be good to have an factory API for creating Exchange that the components uses (DefaultEndpoint). As this allows Camel to optimize certain use-cases by having a hook via the factory API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)