Someone else can comment on our overhead per queue, I have not measured
that, I think we have good support for lots of queues.
You can read a message without consuming it from the queue, and you can
use Ttl ("time to live") to make a message expire when it is no longer
relevant.
The XML Exchange supports server side selectors. Currently, I *think* it
requires the content to be XML. I told someone on Monday that I will
test whether this is true and make it possible to route based on XQuery
for messages that do not have XML in the message body.
But use one queue per client first, the overhead is small, and it will
be less complex.
Hope this helps!
Jonathan
chenta wrote:
How do I send a message to a specific client or a group of client when all of
the client subscribe to the same queue?
I encounter this problem because I do not want to create a queue for each
client. I think it will be a huge overhead for broker when I have more than
15K clients. Am I correct?
Because I am using C++ client so there is no JMS selector support. I don't
think it will be implemented by add an exchange plug-in. Where should I
start if I want to implement this feature?
B.R.
Chenta
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
