Andrea Selva

> Any other workaround? Nothing I'm aware off, simply use MQTT 3.1.1 client to connect to Moquette > like any adapters to mqtt 3 to mqtt 5? There could be...

Hi, why ping requests should be notified with interceptors, which is the use case for an application that embed Moquette to know each ping from every connected client? Il mer...

Hi @djbr-david I understand you requirements, we could have 2 solutions, in my opinion: - make the interceptors aware of the ping from client, but in a configurable manner, with...

Yes, you are right! good catch On Tue, Jul 2, 2019 at 4:58 PM David Brooks wrote: > Thinking of option 2 again, isn't that already covered by the use...

Thank's folks to put down the discussion. I need some time to understand all the pictures you have listed above, I don't like too much to use reference counting for...

Hi @hylkevds for the great summary. The reference counting seems promising. I foresee some points where we need to pay attention. If I understand correctly each thread does a +1...

Hi folks I've some doubts on some sentences: @hylkevds > Which Thread gets the Session when multiple Threads try to revive/terminate the Session at the same time All transitions of...

@jbutler I would suggest to create a PR which focus only on the reference counting, which solves the problem of the missed ByteBuf deallocation when a Session is cleaned, this...

Looking at the a possible thread interleaving that manifest the problem: | time | thread 1 (publisher) | thread 2 (subscriber disconnect) | thread 3 (new connecting client) | |------|----------------------------|----------------------------------|------------------------------------------------|...

Thanks @jbutler! there is no rush, I'll prepare the PR to switch the execution of publish in the peer's socket thread