Hi Tomoaki,
your architecture looks good. You are proposing to alter your
gateway code to use MQTTPacket and MQTTSNPacket, and then contribute
it to Paho?
I had some principles which I adopted for the embedded MQTTClient
API and which I also hoped to adopt for a gateway:
- C++ Standard Template Library (STL) not used – too heavyweight
- system APIs for networking, timing and threading are
implemented as replaceable classes (template parameters in
MQTTClient)
- limited or no other system APIs, for portability
- no heap memory allocation - to make memory use as
predictable as possible
Does your code follow any of those? None of these principles is a
show-stopper - I just want to understand where your gateway fits.
And, just to be clear, a transparent gateway means that a new MQTT
connection is created for each incoming MQTT-SN connection. Is that
your understanding too?
Thanks!
Ian
On 02/18/2016 12:23 AM, Tomoaki
Yamaguchi wrote:
I will propose the Transparent Gateway with MQTTPacket and
MQTTSNPacket.
My gateway architecture outlook is attached.
If you can accept my architecture, I will convert < MQTT-Sn
Message > & < MQTT Message > to MQTTSNPacket
& MQTTPacket.
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev
--
Ian Craggs
icraggs@xxxxxxxxxx IBM United Kingdom
Paho Project Lead; Committer on Mosquitto
|