Ok timefox, remember JINI? A user (call him user A), would ask server A for a .jar file. Server A would look to see if he had it. If not, server A would ask Servers B, C, D ... Z for the .jar file. The server who had that .jar file would send it to server A. Server A would cache it, and send a copy to user A.
Now, lets see how we could do that with JMS! user A asks for all subscribe-able topics. Server A asks servers A through Z for thier topics and presents a list to user A. User A subscribes to topic Q on server Q. So, server A subscribes to topic Q on server Q and when a message is published to topic Q, the message is sent from the publishing user, to server Q, to server A, to user A. This is what we're trying to do, which appears a chore, especially when you add in PKI requirements. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953792#3953792 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953792 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
