We have an environment with 200 clients all subscribing to the same topic. Right now, we use OIL, which as I understand establishes socket connections with the server for each client. Are there separate socket connections for each topic using the same connection factory from the same client? I assume that for a given broadcast, there are actually 200 separate communications (one from the app server to each client?). Is there a more scalable solution involving a true broadcast? What are my options.
You could try out the new (emphasis on 'new') JMS layered on JavaGroups. We use IP multicasting for message distribution, so no TCP connections. This only works if
* Publishers and subscribers are in the same subnet, or are
reachable by mcast
* You don't need durable subscriptions/persistent msgs (not
implemented yet)
* You don't need transactions (not implemented yet)Check out
http://www.jboss.org/index.html?module=html&op=userdisplay&id=developers/projects/jboss/jms
for details.
-- Bela Ban http://www.javagroups.com Cell: (408) 316-4459
------------------------------------------------------- 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/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
