Hello Khaled! I had a vacation, that’s why I am bit late ☺. I am pretty sure there are users which would be interested in the MQTT support. Question is on which level to integrate it. I personaly have a bit different opinion than JinHyeock. I don’t think MQTT client should be integrated as 1st class citizen in the OCF Device. OCF Servers are hosting resources, which might be observed. Currently, CoAP is used, in future, it might be something different. I also don’t think it should be in the gateway, or let’s say MPM as a plugin. In case you want to support many devices in future, you will have to scale and gateway / MPM together with your MQTT broker is not a good maintanable place.
We are currently working on a new cloud, which contains OCF CoAP Gateway. Further communication with other Cloud component will be message based, and MQTT might be integrated. Main idea behind this design is to guarantee interoperability between multiple protocols, introduce multiple gateways, for example for MQTT. Cloud might sound as a buzzoword, but it was defined longer time ago and is well established name. But to make it clear, it’s not something what is supposed to run only in the AWS/Azure/… . It is lightweight (at least new implementation we are working on) and deployable also on a standalone PC. I would propose you to think about it, if this is from your point of view not a better place where to integrate MQTT and reach your goal ☺ We can discuss it deeper throug webex if you’re interested in. Thanks Ondrej @ Kistler From: [email protected] [mailto:[email protected]] On Behalf Of Khaled Elsayed Sent: Mittwoch, 22. August 2018 13:25 To: Gregg Reynolds <[email protected]> Cc: iotivity-dev <[email protected]> Subject: Re: [dev] MQTT G/W Yes, sure. From implementation point of view, I thought of using iotivity-node along with mosca https://github.com/mcollina/mosca. Have already done similar G/W for Bluetooth low energy which can connect to multiple BLE devices supporting three profiles for now. So, the idea is to have the MQTT clients connect to the msoca-based broker which will then have handlers managing the OCF part same as in the BLE case. Another way would be to base on the C API with MQTT mosquito code modified to handle the OCF part. Best Khaled On Mon, Aug 20, 2018 at 8:45 PM, Gregg Reynolds <[email protected]<mailto:[email protected]>> wrote: On Mon, Aug 20, 2018, 1:36 PM Gregg Reynolds <[email protected]<mailto:[email protected]>> wrote: On Mon, Aug 20, 2018, 6:28 AM Khaled Elsayed <[email protected]<mailto:[email protected]>> wrote: Hi, Has anyone developed a MQTT gateway that would host a MQTT broker receiving the MQTT publish requests and creates OCF resources corresponding to the MQTT topics and handles the update of the resources data. It should not be that difficult so I am asking it is already there to avoid doing it again. If it does not exist, would it be interesting for the IoTivity community to have OCF/iotivity and MQTT inter-operability? Speaking in my delusional capacity as voice of OCF community: yes. Just one thing: if you're gonna do this please post your design ideas before you start coding in anger. Lots of ways to do it, you'll wanna get feedback as early as possible. G Gregg -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9896): https://lists.iotivity.org/g/iotivity-dev/message/9896 Mute This Topic: https://lists.iotivity.org/mt/24817907/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
