falconair wrote:
I would like to publish market data through qpid. Since I have massive amount of data flowing through the
pipes, I can't publish all that data to a single topic, since the client may only be interested in one or two
symbols. The usual solution to use a hierarchical topic naming scheme. In other words, rather than
publishing every thing to "level1," I want to split data according to symbols
"level1.msft," "level2.orcl," etc. Clearly I can't have a pre-defined list of topics
in some properties file. What is the best way of solving this?
I am using qpid m4 or MRG (C++ broker) with jms client api.
I assume you are familiar with the topic exchange (used in the
public-subscribe example), and your only question is how to communicate
what topics are available for subscriptions?
Why not keep the available topics on a database on the server, with a
"topic server", a client that reports on the available topics?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
