If MQTT packets are effectively a couple of bytes of header plus payload, and all an MQTT client has to do is check that header, then why not cut out the middle man, send a packet as a couple of bytes of header plus payload, directly receive those packets and check those bytes oneself ?I also doubt the "overhead" of MQTT will be significant for this use case. It reads from a TCP socket and does some very light processing on the first byte or two of data in each message.
I am sure MQTT could be used, I just don't see why it would be necessary, how it makes anything easier, does anything but add unneeded overhead and complexity to things. Just implement what an MQTT Broker and Client would be doing in just a coupe of lines of code in the apps themselves.
The bottom line is adding MQTT into the mix doesn't gain anything. Is additional effort for no return.
Statistics: Posted by hippy — Mon Jul 22, 2024 1:24 pm