You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Therefore there should be an Documents property on the IServiceBusClient<...> interface reflecting this pattern. The property could throw an NotSupportedException when not applicable.
The text was updated successfully, but these errors were encountered:
Hi, yes I played around with the idea of just creating an IBus with only Messages property, which wouldn't distinguish by message type, but still have the endpoint concept. It would probably be done in parallel with ServiceBus rather than extending it.
Splitting the message types like I've done currently does provide some useful asymmetries for partitioning topics and subscriptions, but I can see how people might find a more generic message bus concept useful.
FYI, there is a IMessageBus in Obvs, but currently only has a super basic Subject encapsulating implementation. I use it in prod as a simple internal bus, but you can use the ServiceBus as a local bus now, meaning I've needed it less.
DocumentMessage is one of the Enterprise Integration Patters and should be supported as well as the Event Message, Command Message, and Request-Reply patterns.
Therefore there should be an
Documents
property on theIServiceBusClient<...>
interface reflecting this pattern. The property could throw anNotSupportedException
when not applicable.The text was updated successfully, but these errors were encountered: