You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2007/11/13 15:32:23 UTC
[jira] Created: (CAMEL-215) Add DSL support for LoadBalance
Add DSL support for LoadBalance
--------------------------------
Key: CAMEL-215
URL: https://issues.apache.org/activemq/browse/CAMEL-215
Project: Apache Camel
Issue Type: New Feature
Components: camel-core
Reporter: Willem Jiang
Fix For: 1.3.0
LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
or if can use an out of the box strategy like:
from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
Just a minor twist on that idea; how about
from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
where loadBalance() returns a LoadBalanceClause rather like filter()
returns an ExpressionClause which lets folks pick the strategy of load
balancer to use.
Using a named reference could be by
from(endpointA).loadBalance().ref("someName")...
I also added the idea of using an expression to determine the
endpoints to load balance across as we might wanna support dynamic
load balancing. e.g. querying the endpoints in OSGi or JNDI or
whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-215) Add DSL support for LoadBalance
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CAMEL-215:
-------------------------------
Attachment: (was: camel-215.patch)
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-215) Add DSL support for LoadBalance
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CAMEL-215:
-------------------------------
Attachment: camel-215.patch
This patch just implement configure the load balance endpoints with a static list.
We could add the dynamical endpoints support in the next phase.
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215.patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-215) Add DSL support for LoadBalance
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan resolved CAMEL-215.
----------------------------------
Resolution: Fixed
patch applied with thanks!
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-215) Add DSL support for LoadBalance
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CAMEL-215:
-------------------------------
Attachment: camel-215(new).patch
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-215) Add DSL support for LoadBalance
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40622 ]
James Strachan commented on CAMEL-215:
--------------------------------------
Patch applied thanks Claus & Willem
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-215) Add DSL support for LoadBalance
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40613 ]
Willem Jiang commented on CAMEL-215:
------------------------------------
sorry , it is my fault.
We should create a RandomLoadBalancer here.
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-215) Add DSL support for LoadBalance
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40612 ]
Claus Ibsen commented on CAMEL-215:
-----------------------------------
Is this really correct for the random() strategy (new RoundRobin)?
+ public LoadBalanceType random() {
+ loadBalancer = new RoundRobinLoadBalancer();
+ return this;
+ }
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-215) Add DSL support for LoadBalance
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan updated CAMEL-215:
---------------------------------
Patch Info: [Patch Available]
> Add DSL support for LoadBalance
> --------------------------------
>
> Key: CAMEL-215
> URL: https://issues.apache.org/activemq/browse/CAMEL-215
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Willem Jiang
> Fix For: 1.3.0
>
> Attachments: camel-215(new).patch
>
>
> LoadBalancingProcessor myStrategy; // my own strategy to choose an endpoint
> from(endpointA).loadBalance().setLoadBalance(myStrategy).to(Endpoint1, Endpoint2, ...);
> or if can use an out of the box strategy like:
> from(endpointA).loadBalance().roundRobin(),to(endpoint1, endpoint2, ...);
> Just a minor twist on that idea; how about
> from(endpointA).loadBalance().roundRobin().endpoints().<someExpression>
> where loadBalance() returns a LoadBalanceClause rather like filter()
> returns an ExpressionClause which lets folks pick the strategy of load
> balancer to use.
> Using a named reference could be by
> from(endpointA).loadBalance().ref("someName")...
> I also added the idea of using an expression to determine the
> endpoints to load balance across as we might wanna support dynamic
> load balancing. e.g. querying the endpoints in OSGi or JNDI or
> whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.