[jira] [Comment Edited] (CAMEL-16326) camel-core - Optimize Exchange.TO_ENDPOINT

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen edited comment on CAMEL-16326 at 3/11/21, 9:25 AM:
---------------------------------------------------------------

Optimising for known set property keys to be stored in a quicker way.

TODO: ExchangePropertyKey *DONE*
TODO: api on Exchange *DONE*
TODO: message history
TODO: optimize EIPs and elsewhere in camel-core
TODO: Add note to migration doc



was (Author: davsclaus):
Optimising for known set property keys to be stored in a quicker way.

TODO: ExchangePropertyKey *DONE*
TODO: api on Exchange *DONE*
TODO: optimize EIPs and elsewhere in camel-core
TODO: Add note to migration doc


> camel-core - Optimize Exchange.TO_ENDPOINT 
> -------------------------------------------
>
>                 Key: CAMEL-16326
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16326
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.9.0
>
>
> We could potentially optimize TO_ENDPOINT which is stored as property on the exchange, which takes up an entry in the map. As its commonly in use, we could store it directly on the Exchange.
> pro: no object garbage
> con: new api to retrieve the information



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