Enable Discussions

[winksaville]

This looks interesting, I'm just learning MQTT and I'm wondering why you created this when there appear to be many MQTT crates. If you'd like to talk I suggest enabling Discussions.

Wink Saville

[fabracht]

Hey, thanks for the interest. I'm going to look into the link you posted. Thanks for taking an interest.

[winksaville]

SG

…

On Wed, Dec 3, 2025, 14:02 Fabrício Bracht ***@***.***> wrote: *fabracht* left a comment (LabOverWire/mqtt-lib#7) <#7 (comment)> Hey, thanks for the interest. I'm going to look into the link you posted. Thanks for taking an interest. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH2CHEDVKKRP3HO6OFSKCT375MWXAVCNFSM6AAAAACN2Q4GD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBZGAZDQMJUG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[winksaville]

As stated in my original post, what is your goal here and what makes it different from other MQTT solutions?

[fabracht]

I guess the original objective was to study, but it evolved beyond that.
A few keypoints I had in mind when I started were:

1. Pure async/await, no event loops
2. Complete platform, not just a client
3. QUIC transport with MQoQ - MQTT over QUIC with multistream support
4. WASM support for web browser simulation and testing
5. Unified CLI

Right now, I'm using this to develop this:

A fully managed MQTT arch design tool with Client and Broker simulator. That's where all the WASM implementation comes in handy.

[winksaville]

Nice, how about a link to "that"!

[fabracht]

Haha. There will be one, as soon as I'm done with a "minimal set of features". I can let you know if you're interested. I'll write down a reminder.

[winksaville]

Please do, 🙏