SignalR would work as an alternative, have just an api would work, i mean there are a lot of solutions, we can always write to the rabbitmq directly using the rabbitmq client as well.
but we do want multiple subscribers, we do want persistent queues for retries. the reason why i was asking is, it would be nice if through MT, there would be functionality to not wait for a consumer and specify the destination whether a consumer exists or not. current state, a publish does not really publish unless someone is interested..
what i am referring to is a bit more similar to NServiceBus functionality.
have you implemented anything of the sort using MT?
thank you for your help