[
https://issues.apache.org/jira/browse/CAMEL-16458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-16458:
--------------------------------
Description:
1)
We can look at optimizing this, as if a producer is singleton, then it can be
reused.
The Enricher EIP uses an acquire/release pattern which is only needed for non
singleton producers to be thread safe.
And the same for Poll Enricher (consumer cache) *NO PROBLEM*
2)
And the destination endpoint can be optimized in case its static - then we dont
need to evaluate a dynamic destination.
And the same for Poll Enricher
was:
1)
We can look at optimizing this, as if a producer is singleton, then it can be
reused.
The Enricher EIP uses an acquire/release pattern which is only needed for non
singleton producers to be thread safe.
And the same for Poll Enricher (consumer cache)
2)
And the destination endpoint can be optimized in case its static - then we dont
need to evaluate a dynamic destination.
And the same for Poll Enricher
> camel-core - Optimize Enrich and Poll Enrich EIP
> ------------------------------------------------
>
> Key: CAMEL-16458
> URL: https://issues.apache.org/jira/browse/CAMEL-16458
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.10.0
>
>
> 1)
> We can look at optimizing this, as if a producer is singleton, then it can be
> reused.
> The Enricher EIP uses an acquire/release pattern which is only needed for non
> singleton producers to be thread safe.
> And the same for Poll Enricher (consumer cache) *NO PROBLEM*
> 2)
> And the destination endpoint can be optimized in case its static - then we
> dont need to evaluate a dynamic destination.
> And the same for Poll Enricher
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
