Tomasz Maruszak

I am looking at implementing this feature now. Stay tuned.

You can check out the feature preview: https://www.nuget.org/packages/SlimMessageBus.Host.Memory/2.3.0-rc2 How to use and configure is described in the [memory docs](https://github.com/zarusz/SlimMessageBus/blob/feature/37_memory_blocking_publish/docs/provider_memory.md#asynchronous-publish). There are also other improvements around global error handlers. Feedback welcome.

It is now incorporated into the master. Still in preview until I add a few other requested features: https://www.nuget.org/packages/SlimMessageBus.Host.Memory/2.3.0-rc3 [Memory Docs](https://github.com/zarusz/SlimMessageBus/blob/master/docs/provider_memory.md#asynchronous-publish) Feedback welcome.

@mrochon did you end up integrating with Azure AD via SAML2.0 and this library?

We'd decided to use HTTP Redirect binding, because the POST binding is not supported by this library. I was getting NotImplementedException and also noticed the handling code was commented out....

Can you please review? I've signed the CLA and rebased on latest master. Thank you.

hey @Aghlara, I did not consider on adding DB transport, but I guess it might be an easy way for some applications to start doing messaging without having to provision...

I have started the implementation for this SQL transport. Once a preview version is available I will let you know.

Hi @Juandavi1 could you please elaborate?

Now it is more clear, thanks. I assume you are using Kafka transport, is that correct? There is nothing available out of box, ideally tracing/metrics/instrumentation could be done as a...