Re: [REVIEW] - Optimised toD for HTTP components

2018-04-26 Thread Claus Ibsen
Hi Thanks for the review and comments. Okay squashed and merged on master branch. Lets do optimisations for other components. On Mon, Apr 23, 2018 at 12:50 PM, Claus Ibsen wrote: > Hi > > We have ticket > https://issues.apache.org/jira/browse/CAMEL-12462 > > Its an idea I had though about i

Re: [REVIEW] - Optimised toD for HTTP components

2018-04-26 Thread Claus Ibsen
On Wed, Apr 25, 2018 at 7:29 PM, Alex Dettinger wrote: > +1 > > Great feature, it reminds me an issue years ago where I found a management > context with tons of file endpoint mbeans. The file component provides the fileName uri option using simple expression today that is evaluated per exchange.

Re: [REVIEW] - Optimised toD for HTTP components

2018-04-25 Thread Alex Dettinger
+1 Great feature, it reminds me an issue years ago where I found a management context with tons of file endpoint mbeans. It makes me wonder if the file component would be a good candidate for this optimisation ? Alex On Tue, Apr 24, 2018 at 12:30 PM, Claus Ibsen wrote: > On Tue, Apr 24, 2018 a

Re: [REVIEW] - Optimised toD for HTTP components

2018-04-24 Thread Claus Ibsen
On Tue, Apr 24, 2018 at 11:43 AM, Bilgin Ibryam wrote: > + 1 for this improvement from me. > > toD is very commonly used expression, and while it is an improvement > over recipientList, it has a serious drawback - creating new endpoints > for every changed option... > > Only last week I had to use

Re: [REVIEW] - Optimised toD for HTTP components

2018-04-24 Thread Bilgin Ibryam
+ 1 for this improvement from me. toD is very commonly used expression, and while it is an improvement over recipientList, it has a serious drawback - creating new endpoints for every changed option... Only last week I had to use toD for querying Cassandra, and it quickly became obvious it is not