JanEggers

the issue here is that for websockets we delegate the handling to kestrel. I didnt investigate how to flow the mqttnet tls options into kestrel so maybe there is a...

with the current serializer / api design this is difficult to implement as mqtt requires the size of a message to be encoded in the header. thats why we serialize...

the idea is nice but I think this is a Broker feature as the Broker must relay messages to other cluster nodes. Also I think it is better to have...

maybe we need to pull in Microsoft.Bcl.AsyncInterfaces and make the ManagedClient AsyncDisposable?

@jimsch you could have a look at https://github.com/chkr1011/MQTTnet/blob/2918be18c6c6529584cd1d78e09ebb3fc0819e4f/Source/MQTTnet.AspnetCore/ you maybe can create your own MqttConnectionContext/MqttConnectionHandler and expose / verify the details you need.

I dont know that header thingy or why it should have influence on the remote endpoint property

looks like dupe of #149 somehow but my usecase is different the md itself can be loaded fine but the context for content is wrong

also im not sure why the whole file changed must be some whitespace lineending mess but you can have a look at the change to get an idea what was...

from my pov no dispose / copy is needed. we just need to add to the docs that BasicProperties are only valid until the handler returns just like for the...

I think the public api is and should be an interface. And I think it should be implemented as a class to avoid boxing and copiing. Also the instance itself...