On 7/20/06, Kuppe <[EMAIL PROTECTED]> wrote:
One final question on this topic - is there additional technical overhead in the broker managing large numbers of topics, for example one topic per user per symbol? Of course this could grow very quickly with the number of users...
Topics are intended to be consumed by many consumers; so 1 topic per symbol is fine. You can then use the last image caching to get a market data cache as well :) http://incubator.apache.org/activemq/subscription-recovery-policy.html
There is certainly an administrative/support overhead in that monitoring the number of topics through a JMS console will be more cumbersome, but this is another story... Any thoughts on how best to handle this?
So I really just mean on startup... * subscribe to the advisory topics you're interested in * connect to the broker via JMX and query the current consumer state * now just watch advisories Otherwise your program could terminate, restart and miss messages. i.e. think of it as using JMX as your 'last image cache'.. -- James ------- http://radio.weblogs.com/0112098/
