[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Fwd: [xmlblaster] oid or xml key ?]
Nelson Silva wrote:
Yes, it is called history queue.
I've come up with this explanation so far:
- The server has TopicHandlers and has a queue for each topic.
- These topics/queues are identified by an oid
Yes, from the <key oid='...'/>
- There are several messages in a queue.
- Clients subscribe to these topics/queues with exact queries or using
Yes, to the message events.
If you are using java:
My question now is.. can i subscribe to a single topic many times
using different XPath queries on the Qos and having a different
callback for each subscription?
SubscribeReturnQos subscribe(SubscribeKey subscribeKey, SubscribeQos
subscribeQos, I_Callback cb)
If you use C++:
org::xmlBlaster::client::key::SubscribeKey& key, const
org::xmlBlaster::client::qos::SubscribeQos& qos, I_Callback *callback=0);
Those client side methods dispatch the messages on client side to the
For other programming languages you need to dispatch yourself.
I'm thinking of using multiple subscribes and the XPath Qos queries
available in the subversion repository...
Hope i'm on the rigth path .. any comment/suggestions are welcome =)