Hi, I have java GUI clients which connect to a clustered JBoss server environment via JMS. So far I was using JMS topics to broadcast certain message to a topic all clients where subscribed to. This turned out to be a great waste of bandwidth because most message are only relevant for a small subset of clients.
So I thought about it and came up with two possibilities to address this issue: #1 Because of the pub/sub nature of topics I thought that possibly point-to-point message queues are better suited for my problem. I want to be able to publish messages from a MBean on the server side to specific clients. Because I need one queue per client and I don't know how many clients will log into my system. I think I will need to be able to dynamically created queues. I briefly looked into temporary queues but the API said that one can only use them within the same queue connection, which makes them unusable for me. I know that queues are just MBeans so I thought of creating them through a bean call and returning the unique JNDI name to the client which would look the Queue up and be able to subscribe. I might also have to think of something in case the JMS node in the cluster dies and dynamically recreate the queues. #2 Poll the app servers a few times a minute using ordinary bean calls and forgetting about JMS. Disadvantage is that I will have a possibly bigger latency until the client will get the information than it would if I would use JMS. Waste some bandwidth for unnecessary bean calls. Any feedback and alternative ideas are welcome. Regards, Sebastian ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
