Hadrian Zbarcea wrote:
>
> Hi,
>
> Sorry for the confusion. DR is a pattern and can be used many more
> scenarios than the one I mentioned. We intend to properly implement DR,
> not merely support that scenario.
>
> From your patch it looks that you want to load balance. I assume you
> know that camel already supports load balancing. You could take a look
> at
> camel-core/src/test/java/org/apache/camel/processor/LoadBalanceTest.java.
> Here's the relevant excerpt:
>
> from("direct:start").loadBalance().
> roundRobin().to("mock:x", "mock:y", "mock:z");
>
> Cheers,
> Hadrian
>
>
Nope. The idea was to create dynamic routing in one expression, LB was for
testing purposes. Probably it was also doable using recipient list and
providing class that dynamically evaluates to list of endpoints -
.recipientList(new MyExpressionImplementer()) - it proves that it wasn't
good (such functionality was provided already).
However if we wanted to implement DR according to Gregor's definition what
would you suggest?
Probably it could be implemented as a structure like one consumer endpoint
that consumes messages with rules/endpoints that feed registry with rules
and DSL like .dynamicRouter(...) somewhere that could create dynamically a
list of recipients using that registry and send messages. Both routing and
managing rules would be dynamic. What do you think about it? Probably it
would be good if the control channel endpoint was implicitly created.
btw, happy new year! :)
--
View this message in context:
http://www.nabble.com/-jira--Created%3A-%28CAMEL-280%29-Dynamic-Router-implementation-tp14523401s22882p14527506.html
Sent from the Camel - Development mailing list archive at Nabble.com.
