I just tried your solution, it works :)
I didn't realize I could create topics on the fly.
falconair,
Since I don't do this kind of thing myself, I may not understand all of
the issues in your application domain. Let me see if I understand what
the issues are.
1. There are many topics. You w
falconair,
Since I don't do this kind of thing myself, I may not understand all of
the issues in your application domain. Let me see if I understand what
the issues are.
1. There are many topics. You want to use hierarchies to manage them.
Wildcards do that well in the topic exchange.
2. Y
falconair wrote:
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
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
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
Hi think Headers exchange might be the one I need. Unfortunately I can't find
any developer-friendly docs on it. MRG manual doesn't mention it and
qpid.apache.org doesn't seem to describe how to use it from a Java client
(google doesn't help much).
Any pointers on how I can access Headers ex
2009/3/24 falconair :
> After sending the original message, I realized that I might be able to take
> advantage of selectors or 'where clause' like functionality. In other words,
> I could subscribe to level1 but limit the values to "symbol=MSFT" (which
> means only MSFT should travel down the
falconair wrote:
The main reason I can't have pre-defined topics (in properties file or
database) is because symbols are changed every day (some may be added, some may
be deleted, some may just change slightly).
Maintaining an accurate list of these symbols is not trivial (some large banks
ha
The main reason I can't have pre-defined topics (in properties file or
database) is because symbols are changed every day (some may be added, some may
be deleted, some may just change slightly).
Maintaining an accurate list of these symbols is not trivial (some large banks
have groups dedicate
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 nami
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 nami
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 ot
12 matches
Mail list logo
