> >Also, sorry for not mentioning it before (I didn't really look at the > >details, I have to admit ;-) Too busy :-(), but I have a problem with JG's > >license. Basically, I don't want to create any dependency to it, > >and I don't > >want JG to be part of the TC build process. > > it doesn't have to be, it can be as Jason explained, we can create hooks and > interfaces, > that way the user/sys admin can choose which module to use for the comm, be > it JG, Spread or something else. You just say the word. > > >So sorry, but I'm not very interested in the contribution anymore. The > >functionality is useful, obviously. Maybe you should distribute it as a > >module for your project. > > sorry to hear that. > > Let me know if you change your mind, and want me to create the hooks and > interfaces to allow you to plug in any messaging system. Also this way, the > TC build would not be dependent on any outside library.
That kind of design would be more interesting. I was probably too harsh in my response; I just wanted to point out I made a mistake by being that enthusiastic about it originally. I think I'll create a 'cluster' component in j-t-c, as was suggested, and move the existing cluster implementations there. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
