tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fcarr...@elektra.com.mx
Subject Re: Congrats on Summer of Code proposal selection
Date Thu, 25 May 2006 20:50:44 GMT
Hi,

I actually developped a ClusterSingleSignOn for Tomcat. It is available on 
the same website :
http://wwwetu.utc.fr/~fcarrion/GoogleSoC.html
I followed exactly my applying in the google summer of code. There you can 
find every thing, the patch for tomcat 5.5 and my doubts especially about 
mbeans-descriptor.xml

Feedback are welcomed =)

I'm currently implementing a communication layer between cluster tomcat 
nodes using JMS. But I got some doubts too :

- To connect on a JMS server, I register the connection factory in the 
tomcat context as a Resource. But I got a problem, when I want to access 
to the connection factory in the tomcat context from the start function in 
my cluster implementation, it seems that the context is not yet 
initialized... So I can't access to my resource.

- There is three way to send a ClusterMessage in a Tomcat cluster :
sendMessage : to send a message to all the members registered in the node
sendClusterDomain(Domain) : to send a message to all the members 
registered in the same Domain in the node
sendMessage(Member) : to send a message to one member especially
I'd like to know if the functionality to send a message to a specific 
member is used. Because if it is not used, I don't have to developped a 
membership functionality, for the simple fact, that all the members are 
connected to the same topic, and they don't need to know which is alived 
and which is not.

- The JMS specification say when you want to connect to a topic, you have 
to set a client ID, different for every clients. In the current cluster, 
the ID used is the association Host + port, but I can't do that, because I 
don't know the port. So I ask the user to give an ID. It's not a good 
solution (in my mind) a friend point me this solution :
UUID implemented by http://jug.safehaus.org
I dunno if it could be usable...

Any idea ??
Well that's all for now

Cheers'


-- 

Fabien Carrion

()  Campagne du ruban ASCII -- Contre les mails en html
/\  contre les pieces-jointes Microsoft
Web: http://wwwetu.utc.fr/~fcarrion




"Yoav Shapira" <yoavs@apache.org> 
Enviado por: yoavshapira@gmail.com
24/05/2006 02:16 p.m.
Por favor, responda a
"Tomcat Developers List" <dev@tomcat.apache.org>


Para
Tomcat-dev <dev@tomcat.apache.org>
cc

Asunto
Re: Congrats on Summer of Code proposal selection






Hi,
It actually looks like this project was among the 1800 that were
mistakingly accepted and then finally rejected by Google [1].  Please
ignore my previous message from earlier today, and consider the
project open to anyone who wants to contribute.

Yoav

[1] Google announcement and discussion thread:
http://groups.google.com/group/Summer-Discuss-2006/tree/browse_frm/thread/71dcb003247ee84d/0edab71113a7d53a?rnum=1&_done=%2Fgroup%2FSummer-Discuss-2006%2Fbrowse_frm%2Fthread%2F71dcb003247ee84d%2Fe79c306e2c99362b%3F#doc_0edab71113a7d53a


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org





-----------------------------------------
La información transmitida mediante el presente correo es para
la(s) persona(s) cuya dirección aparece al calce, la información
contenida es estrictamente confidencial y para lectura exclusiva de
la (s) persona (s) mencionada(s) por lo que esta prohida la
reproducción, distribución o copia del presente. Si usted ha
recibido este correo por error, favor de contactar con el remitente
y eliminarlo de todas las charolas de su correo. The information
transmitted by this e-mail is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. If the reader of this message is not the
intended recipient, you are hereby notified that you have received
this message by error and that any review, dissemination,
distribution or copying of this message including any attachments
is strictly prohibited. If you received this by error, please
contact the sender and delete the information from any computer.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message