Hi Kov,
I will try to go comment by comment below.
Thanks for this > @kov said:
Hi Ali, thanks for the additional context. I thought I’d responded but our community board software seems to have eaten it, so let’s try again and my apologies for the delay:
No probs, one of my posts some how disappeared as well. There is some issue in the forum setup I guess.
FLOWS: FlowReceivers are a PERSISTENT messaging concept; they only apply to persistent endpoints that save messages for you until you consume and acknowledge them
CACHES: Cache requests are a DIRECT messaging concept; they do not work with persistence so cache results cannot come through your queue consumers
I don’t think topic-dispatch would have helped you to unify those two flows because of this.
We dont want to unify the flows. If you look at the SolaceSessionAPI interface example that I pasted above we are fine with having seperate methods for topic, queue and sol-cache topics. We just ideally want to get it done with min no of tcp connections/sessions.The question for you is – can you mandate publishers put a schemaID on their messages identifying the payloads? Or is this outside of your control?
Changing all the message publishers will probably not be possible for us. I think the best solution for us is to have a custom topic dispatcher for topics and sol-cache topics. Maybe we can experimenting with using Spring reactor or RxJava etc or it might be an overkill … not sure yet.
Thanks,
Ali