Why is MQTT supported both as an Adaptor and a Driver?

[Jay Newman]

Hello,

I'm new to Gobot, but I am working hard to understand it. I have Gobot installed on three machines, my linux laptop, a Raspberry Pi 3B+, and a Raspberry Pi Zero W. Just today I managed to get simple communication working between my laptop and the Pi Zero W. I used the Adaptor version.

What I'm curious about is why there is both an Adaptor and a Driver version, and which should I be using.

Probably later this week I will work on using the Driver version and making the communication less simple.

Thanks to all for providing this framework.

-

Jay

[Ron Evans]

Hi, Jay

Generally speaking in Gobot an Adaptor handles the communication with something, and a Driver is what knows about behavior.

For example, the Raspberry Pi Adaptor implements the GPIO interface, and the LED Driver consumes the interface to be able to implement its own Toggle() function.

In the case of MQTT the Adaptor handles the communication with the MQTT server. The MQTT Driver is intended as a convenience to serve as a sort of "virtual device". Some IoT cloud services call them "device shadows".

Anyhow, hopefully that explains a little better what is intended here.

[Jay Newman]

Ron,

Thank you very much. It explains it well.

-

Jay