Hi Nick,

I would keep the names of all the topics in a replicated cache. Every server 
and client will have access to it and can retrieve all the topics' names stored 
there and subscribe for them after that.

Does this work for you?

—
Denis

> On Jun 3, 2016, at 3:49 AM, nickg <[email protected]> wrote:
> 
> Hi all,
> 
> I'm currently writing a messaging application using Apache Ignite (for a
> proof of technology), and was using  Topic Based Messaging
> <https://apacheignite.readme.io/docs/messaging>   for the communications.
> 
> Everything works well, *IF* the two clients/nodes have agreed on a specified
> topic name first.
> e.g.
> rmtMsg.remoteListen("MyOrderedTopic", (nodeId, msg) -> { ... })
> 
> What I'd like is to be able to discover the list of available topic names,
> that have nodes listening, from any client/node - so that the nodes don't
> have to know before hand which topic to subscribe to.
> 
> *What I've tried?*
> I had a dig around, and was able to find the topic name in the 
> GridMessageListenHandler.java
> <https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/GridMessageListenHandler.java>
>   
> class (I think) ... how do I get these from my ignite context?
> 
> Kind regards,
> Nick
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Discovering-Topics-that-are-being-listened-to-tp5388.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to