Tomasz Maruszak

Hello @apitzele , the consumer side takes the declared type and tries to deserialize arriving messages into that type. No filtering is implemented nor was intended as SMB is simple...

On a related note, I have plans pas the message type as part of the message headers (for transports that support message headers). This is to not have to rely...

I created an issue to add message type in the native message headers for supported transports. Beside the filtering scenario I have some other use cases for that. Feel free...

Can someone please re-trigger the build as it failed?

With the recent change #130, it should be possible to push multiple message types via one event hub. See the [docs](../blob/master/docs/intro.md#multiple-message-types-on-one-topic-or-queue).

Some more samples: MQTTnet: https://github.com/dotnet/MQTTnet/blob/master/Samples/Client/Client_Publish_Samples.cs https://github.com/dotnet/MQTTnet/blob/master/Samples/Client/Client_Subscribe_Samples.cs Azure IoT Hub: https://github.com/Azure-Samples/iot-hub-mqtt-5-preview-samples-csharp/blob/main/src/Program.cs https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support

Nothing has been done yet that I am aware of. Let me know if you're willing to work on the implementation, otherwise I will start this.

Will use this client to implement the Rabbit transport: https://www.nuget.org/packages/RabbitMQ.Client I have started the implementation.

The RebbitMQ transport is available: https://github.com/zarusz/SlimMessageBus/blob/master/docs/provider_rabbitmq.md The preview version is available: https://www.nuget.org/packages/SlimMessageBus.Host.RabbitMQ Feedback is welcome!

Well, I am more than open to having this feature, just there are other areas I am evolving SMB on at the moment. I am open to contributions from the...