MQTT simple API about micropython-lib HOT 2 CLOSED

Could we rethink mqtt api as it is now?

Generally, no. There was RFC for MQTT implementation: micropython/micropython#2055, people who were interested participated in the discussion and affected how it was implemented. But it's implemented now.

Unfortunately as many other libraries I see that mqtt.simple tries to make it's own 'socket'.

I'm big fun of dependency injection pattern myself, but others don't have to (be fan of it or even understand it), see for example micropython/micropython#2285 (comment) . Also, it has limits on its use to. For MQTT support, there was (implicit) requirement that it was easy to use, and there was "robustness" support (also easy to use), so socket is the part of the controlled state.

you will start to bloat protocol api with socket/ssl options

Addressed by 98c6fb9.

So, what you think?

You can always write your MQTT implementation (and popularize/support it).

from micropython-lib.

I see, missed that, sorry than...

ssl_params seems that as good enough solution

2016-08-24 0:23 GMT+02:00 Paul Sokolovsky [email protected]:

Could we rethink mqtt api as it is now?

Generally, no. There was RFC for MQTT implementation:
micropython/micropython#2055
micropython/micropython#2055, people who were
interested participated in the discussion and affected how it was
implemented. But it's implemented now.

Unfortunately as many other libraries I see that mqtt.simple tries to make
it's own 'socket'.

I'm big fun of dependency injection pattern myself, but others don't have
to (be fan of it or even understand it), see for example micropython/micropython#2285
(comment)
micropython/micropython#2285 (comment)
. Also, it has limits on its use to. For MQTT support, there was (implicit)
requirement that it was easy to use, and there was "robustness" support
(also easy to use), so socket is the part of the controlled state.

you will start to bloat protocol api with socket/ssl options

Addressed by 98c6fb9
98c6fb9
.

So, what you think?

You can always write your MQTT implementation (and popularize/support it).

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#93 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFlRAjZpHGUxOXSdFlYlESvU_1XHK7pXks5qi3LEgaJpZM4JptdL
.

Jan Koniarik
[email protected]

from micropython-lib.