> >From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] > >>Move it out of the core, it adds complexity. Leave/add any hooks you > >>need, but keep the bulk of the code/interfaces out, in a separate > >>module. > >> > >>I would even sugest j-t-c, since it's likely to need some of the > >>things there ( unix sockets, shmem, etc ). > > > >+1 > > We can put it anywhere, I wrote the implementation as a plug in, without > modifying one single line of code in the current catalina implementation. > However, we are talking about three classes, that could be greatly enhanced > in the core as opposed to always catching up with the API changes that > occur. > It is not very complex at all.
I got the classes, and briefly looked at it. I didn't have time to actually test it, but it looks well worth committing. My main gripe with the contribution at the moment is that it does not respect at all the coding style used in the rest of Catalina. So the patch will get in when I take the time to do some reformatting ;-) After that, I'm +1 with giving you commit access if you plan to continue contributing (and wherever the cluster component ends up, we need a maintainer for it). Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
