Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
definitely the modules/ha and modules/groupcom.
I'd like to clean it up first though, my idea is to instead of
configuing all the messaging inside the <Cluster> element, the actual
Tribes impl I'd rather configure as a JNDI resource,
this has a some benefits, to mention a few
- more components can take advantage of it, such as monitoring tools,
other cluster implementations etc
- Avoid having a giant blog that takes up half of server.xml when
clustering is turned on
- Separate out IO tuning from replication configuration
I know in the past other people felt the need for these to be
modules, for me I dont care either way, I think it might be good for
us to get a consensus before I merge it in.
You mind sitting a couple of weeks on it and let folks chime in while
I work on the config separation?
The problem I have is that the other persons who contributed heavily
to clustering seem quite uncomfortable (or at the very least,
overwhelmed) with the new implementation at the moment. Personally, I
also prefer a server.xml configuration.
Then its probably wise of use to let this sit for a couple of weeks and
hash it out. The replication logic hasn't changed, its the underlying
messaging that has been separated out logically.
Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
