Martin Regen

Hi @chkr1011 , thanks for your guidance. In MqttPublishPacket sounds good to only carry PayloadSequence for newer .NET versions. I'm fine with your suggestion and hopefully provide an update soon.

Hi @nelsonmorais, I can repro the issue when neither revoked nor CRL extensions are encoded. As a workaround you can add a CRL extension or revoke a cert. Otherwise fix...

Hi @chkr1011, I am now looking into the option of passing a RecyclableMemoryStream (or a custom MemoryStream) into the reader to also benefit from better buffer management using ReadOnlySequence on...

> @mregen I never used that RecyclableMemoryStream before. The idea of not increasing the buffer every time (only doing this one time when GetBuffer is called) looks like a reasonable...

Hi @chkr1011, please have a look now and provide feedback. From my side the functionality for buffer ownership handling is included. Apparently there is a breaking change in the client...

Hi @chkr1011, thanks for the feedback.. > @mregen > > > To overcome the issue the application can either transfer the ownership of the payload in the application message and...

> In my opinion we should introduce a new property in the client and server options with the same naming. For example, "EnableManualPayloadManagement" or similar. Then the summary tag should...

Hi @chkr1011, the receive codepath is getting too complicated. I created a minimal version with ReadOnlySequence support in #2046 to get started with the publish support with hopefully better chances...

I tried to test your library and I am getting errors due to transitive vulnerabilities, I presume because of the dependency on netstandard1.3 which is out of support: ``` Restoring...