Christopher Hunt

As an adjunct to this issue, I had an SSL cert expire on a backend that had been configured as `ssl verify none`. Yet, when that backend's cert expired, the...

@sbmpost FYI I'm no longer involved with this project. Thanks for the notification.

Thanks for the fix - can we please first have a test that fails for the existing code?

> Tried to create a unit test but could not reproduce it using alpakka streaming client side since it will never send two PUBLISH QoS2 messages in a row to...

> I might be missing something, but haven't seen anywhere in the MQTT spec that this behaviour is not legit, I mean, sending two publish Qos2 messages with different packet...

The server design is such that only one publish for a topic can be processed at a time. Allowing more is going to break ordering as there will need to...

> The only spec I found is the one you point me out and as I said it is not violated on the client side at all Sorry, by spec,...

Thanks for the tests - we probably only need the one i.e. either the client or the server - perhaps just the client. Given that there's no difference in behaviour...

> I think MQTT spec doesn't imply sending two publish messages at once is wrong by itself (as long as mandatory rules are fulfilled) The potential is for there to...

How many publish messages should we potentially allow to queue up for a given topic?