You are right, that is indeed how I currently use qpid. However, for
marketdata, there might be thousands of symbols.
Currently, every topic I use has to be defined in my properties file as such:
topic.a=x.a
topic.b=x.b
...
I can't list all the symbols (once for level1, again for level2 then again for
timeandsales): partly because the properties file would grow too large, partly
because managing these symbols (and their changes) would be a nightmare.
That's why I wanted to define some top level topics (level1.*, level2.*, etc.)
and somehow avoid having to pre-define the topics at the symbol level
(level1.msft, level1.orcl, level1.ebay...).
I think the solution is to use Headers exchange (if it works through JMS)
Forgive me if I'm being over simplistic, but isn't that exactly what the
topic exchange gives you?
I.e. you publish your data using "level1.msft", "level2.orcl" etc as the
routing key and then your subscribers can bind queues as appropriate.
E.g. "level1.msft" would only match that exact symbol
"#.msft" would match level1.msft or level2.msft
"level1.#" would match all level1 symbols
You can bind the same subscription queue more than once, so you can set
it up to e.g. receive anything matching "#.msft" or "#.orcl". How
exactly you do that using the binding URL syntax for the JMS client I
will leave to those more qualified to comment.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
--
View this message in context:
http://n2.nabble.com/how-to-programatically-create-thousands-of-topics-%28for-marketdata%29--tp2528658p2532404.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
