jtc could became jakarta-tomcat-commons, a repository
of stuff used by tc 3 and tc 4

I'd like the idea of jtc/cluster where filip could create
interfaces implemented by :

- javagroups (outside apache)

- spread (inside apache with their bsd like license)

- rawsocket (quck&dirty tcp implementaion spreading messages to a
             list of known tomcat)

- jdbc (use a sql backend)


-
Henri Gomez                 ___[_]____
EMAIL : [EMAIL PROTECTED]        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-----Original Message-----
>From: Filip Hanik [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 13, 2002 9:50 PM
>To: Tomcat Developers List
>Subject: RE: In memory session replication, reminder
>
>
>>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.
>
>Filip
>
>~
>Namaste - I bow to the divine in you
>~
>Filip Hanik
>Software Architect
>[EMAIL PROTECTED]
>www.filip.net
>
>
>--
>To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to