Question: Request/Response syntax? about async-mqtt HOT 4 CLOSED

Hi @RangerMauve, that's a good idea, thanks for your replies. I'll let you know if/when I'll publish the project

from async-mqtt.

Hi there!

Your idea is actually amazing and I find it very interesting, but the purpose of this repository is to only provide a promise wrapper around the MQTT.js. I don't think that this relates to here.

But it's an idea that I actually craved about. To define routes for MQTT.

Also, I think that the topic you mentioned should be generalized more. For example instead of converting my/topic to my/topic/request/{id} maybe its better to use it this way my/topic/request/{id} to better describe the topic.

from async-mqtt.

Hello!
Yeah you're right, I thought it was a good idea to not have 65 different clients with 65 different features each, but I think I'll just make my own at this point to not bloat this one.

Can you elaborate on the part about topics? I didn't understand what you mean.

from async-mqtt.

Hi @MatteoJoliveau, I agree with @Tabrizian about your requests model not being in-line with the goal of this library. This client is really made to be general purpose and lower level.
The request thing you have is interesting, but I think it's very specific to your use case.

If you end up using this as a dependency, I think it would be fine for us to mention your library in the README in a projects using this section so that people can find your library more easily.

from async-mqtt.