[
https://issues.apache.org/jira/browse/CAMEL-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447930#comment-16447930
]
ASF GitHub Bot commented on CAMEL-12462:
----------------------------------------
davsclaus opened a new pull request #2302: CAMEL-12462
URL: https://github.com/apache/camel/pull/2302
See ticket: https://issues.apache.org/jira/browse/CAMEL-12462
Anyone is welcome to take a peak and provide feedback. This PR can be
squashed and merged when its done.
We can do this kind of optimisation for other components as well, for
example JMS with the CamelJmsDestination header for the JMS queue/topic.
However JMS uses a connection pool so its fairly optimised as well, but it
would still use a new producer per different queue/topic.
----------------------------------------------------------------
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]
> toD with HTTP endpoints - Optimise dynamic query to leverage HTTP_QUERY header
> ------------------------------------------------------------------------------
>
> Key: CAMEL-12462
> URL: https://issues.apache.org/jira/browse/CAMEL-12462
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 2.22.0
>
>
> We can consider for some HTTP components that support dynamic parts of their
> endpoints from Camel headers such as HTTP_QUERY and others.
> We can then in toD detect those components and then build a processor chain
> that does
> # setHeader - set dynamic header HTTP_QUERY
> # toD - call the endpoint with a more static uri
> This optimises to reuse the toD with more static uris, especially if you hit
> the same host for each toD and its only the query parameters that are dynamic.
> Today developers would need to use setHeader and to combo to do this, instead
> of a single toD.
> The trick is to separate the query parameters and the endpoint parameters and
> only set query parameters in the setHeader, and the endpoint parameters in
> toD.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
