Am 23.02.2006 um 16:51 schrieb Rainer Jung:
Hi Filip,
thanks for taking it seriously!
1. If we don't primary/secondary will not be available until TC.6
> 3. Many people are opting out of clustering today because of lack of
> primary/sec. all-to-all is too inefficient for the general public
Hey Rainer, Filip and Remy,
Am 23.02.2006 um 17:20 schrieb Rainer Jung:
Hi Remy,
1. If we don't primary/secondary will not be available until TC.6
2. TC 6 doesn't have a skeleton nor a date yet.
It could have that tomorrow.
...
I agree with Peter: it's obvious no one should be doing major
Many thanks!
I thing the best way is to move the new cluster implementation at a
new cluster2 module.
With the current cluster build system it is easy to generate and copy
the calalina-cluster.jar to tomcat local build directory.
The only problem currently is ClusterRuleSet must be move fro
Hi Remy,
1. If we don't primary/secondary will not be available until TC.6
2. TC 6 doesn't have a skeleton nor a date yet.
It could have that tomorrow.
...
I agree with Peter: it's obvious no one should be doing major
refactoring of existing components in 5.5.x. You could create a separate
Filip Hanik - Dev Lists wrote:
Rainer, all are very good thoughts. Here is why I opt we still move forward
1. If we don't primary/secondary will not be available until TC.6
2. TC 6 doesn't have a skeleton nor a date yet.
It could have that tomorrow.
3. Many people are opting out of clustering
Hi Filip,
thanks for taking it seriously!
1. If we don't primary/secondary will not be available until TC.6
> 3. Many people are opting out of clustering today because of lack of
> primary/sec. all-to-all is too inefficient for the general public
I understand your primary motivation. It#s tru
Rainer, all are very good thoughts. Here is why I opt we still move forward
1. If we don't primary/secondary will not be available until TC.6
2. TC 6 doesn't have a skeleton nor a date yet.
3. Many people are opting out of clustering today because of lack of
primary/sec. all-to-all is too ineffi