tibboh
tibboh
Thanks! I'll clean up my implementation and send PRs in the order described above.
Hi, I didn't have time to clean up my code and probably won't be able to do this for the next month or so. I do think the graph should...
@ttichy I'm curious about your solution. You say that you store the message with key=mid prior to publishing. But isn't mid available only after you call ``publish()``? With QoS=0, ``publish()``...
I'm seeing the same behavior. It makes it quite difficult to build a client-side persistence layer (you don't know the ``mid`` until ``publish()`` returns, but in ``on_publish()`` you want to...
This could be solved by allowing per-message callback argument in ``publish`` (which I've seen planned somewhere in the docs). Then we could: * generate a unique ID * store the...