Posted: Wed Apr 15, 2009 3:29 am Post subject: Topic Trees
Chevalier
Joined: 05 Nov 2005 Posts: 401
The documentation makes it clear that it is not necessary to create a topic tree in advance, and perhaps not at all ?
Quote:
Topics can be defined by a system administrator using the workbench. However,
the topic of a message does not have to be defined before a publisher can use it; a
topic can also be defined when it is specified in a publication for the first time.
I am thinking about developing a flow that receives messages (actually from an external organisation) and publishes them to a number of topics that internal applications might 'subscribe' to. As per pub/sub, publishers and subsribers should know nothing of each other and, in this case, I don't really want/need the producer of the message that will be published to know the internal details of my topic hierarchy either. So the flow itself will determine the appropriate topic, add the RFH2 stuff and pass everything to a publication node.
Does that sound reasonable ?
I am wondering what advantages there are of creating the topic tree up front, or even if I need to do that at all in this scenario ?
I guess that applying ACLs might be easier and possibly a requirement if subscribers/topics need to be secured (although I don't need them in this case - yet anyway) ???
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum