Swanand Mulay

> because the key is not a real private key, instead it's some unique ID and an "Engine". > Job of engine should be done by we get the pkey...

Hey, Thank you for the detailed explanation! I was investing it further and noticed rustls docs have a field with [max_fragment_size](https://docs.rs/rustls/latest/rustls/client/struct.ClientConfig.html#structfield.max_fragment_size) which by default sets limit of 2**16 ( 64KB...

I did try the code you shared, with only one change as I don't have to custom_cert_verifier, I used my own valid certificates: ```rust let mut alpn: Vec = Vec::new();...

also, one intresting thing I noticed is that, it's not about any activity, it has to be pingreq for some reason haha. E.g. - publish that big message - subscribe...

BTW, can you please once confirm if issue still exists if we use different brokers like hivemq or emqx, etc.?

Breaking changes are those changes which affect/change the behavior, in this case, think of it like previously we would disconnect/disallow subscriptions to topic with `$` prefix, but with this PR,...

so something like, `publish` will return `Pkid` where: ```rust struct Pkid { id_rx: Receiver, } impl Future for Pkid { type Output = u32; fn poll(..) -> .. { //...

> Include it in the request? > gotcha. so unlike https://github.com/bytebeamio/rumqtt/compare/main...pkid-poc , by using the channels we are avoiding direct use of `Arc` ! > [Not in the case of...

I just glanced over the changes, this is really clever way to so it haha, glad that you figured it out! :smile: The idea of **_adding_** the ability to specify...

`Notification::Disconnect` was introduced in https://github.com/bytebeamio/rumqtt/pull/616 so that we can send `Disconnect` packets to v5 clients ( which was the best way I could think of at that time ) Guess...