Thank you MyeongGi and Uze. Can you point me to where the document folder is located? Thanks
From: MyeongGi Jeong [mailto:[email protected]] Sent: Tuesday, January 5, 2016 8:19 PM To: Pardee, Thomas C <thomas.c.pardee at intel.com>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTivity Extension for MQTT Hi, Thomas. Discovery & Connectivity TG has already discussed about MQTT supporting. You can see the draft proposal document in the document folder. On the other hand, we have also checked CoAP-MQ. They show the simlar way to enable pub/sub using the broker object. I guess, we need analysis which is more desirable. Thanks. Best Regards, --- MyeongGi Jeong Senior Engineer, Software Architect Software R&D Center, Samsung Electronics Co., Ltd. +82-10-3328-1130 | +82-2-6147-7699 ------- Original Message ------- Sender : Pardee, Thomas C<thomas.c.pardee at intel.com<mailto:thomas.c.pardee at intel.com>> Date : 2016-01-06 09:38 (GMT+09:00) Title : [dev] IoTivity Extension for MQTT Hi, I?m looking at using IoTivity and MQTT. If IoTivity were to be extended to support MQTT, would it be better to create a new plugin like the Zigbee plugin or to create a new OCTransportProtocolID for MQTT in addition to CoAP? [cid:image001.gif at 01D14869.C4F5BCE0] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=f00c83e4556b95b99fa35af64c78645a58ef0e8a7653647a032aa89e99be1a3e5620e5df2600f63e6f03626e986c2b1d09060032c89b30e00407d1a278fe738d3298a32fe7c0f484cf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160106/04e726c7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160106/04e726c7/attachment.gif>
