Re: [dev] MQTT G/W

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

[dev] notice: valgrind turned off on master

I went ahead and made a maintainer's decision on the buildsystem: I merged https://gerrit.iotivity.org/gerrit/#/c/26757/, which turns off running the unit tests under valgrind control. We don't really want to lose the information gathered from this, but at the moment the unit tests builder is ju

Re: [dev] Major issues with connecting to cloud using TLS

> in implementing a device you would have it update the actual storage. Are there any examples for doing this on Android? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9894): https://lists.iotivity.org/g/iotivity-dev/message/9894 Mute This Topic:

Re: [dev] Major issues with connecting to cloud using TLS

On 08/22/2018 02:39 AM, yitzc...@coapp.co.il wrote: >> the "secure resource" is just an (insecure) file which it wouldn't be on a >> real device > What should be used on a real device? a real device has real secure storage. iotivity uses a "virtual" resource, which can be backed by a file like i

Re: [dev] MQTT G/W

Hi Khaled, It was not dropped but it did not get any update due to lack of demand. You can find some information at below links – https://wiki.iotivity.org/protocol_plug_manager_for_linux https://wiki.iotivity.org/release_note_0_9_2 Regards Dwarka From: iotivity-dev@lists.iotivit

Re: [dev] MQTT G/W

Hi Kishen I am not proposing using MQTT as OCF transport. Just as you mentioned below > However, I assume your comments were coming more from an open-source > tool perspective, in that establishing OCF<->MQTT interop in IoTivity might > enable developers to more easily prototype IoT application

Re: [dev] MQTT G/W

Great to know there is good interest and intention to launch project in that direction. I would probably be working on some quick and dirty gateway implementation to demonstrate the concept. On Tue, Aug 21, 2018 at 10:00 AM, 최진혁 wrote: > Hi > > > > If it does not exist, would it be interesting

Re: [dev] MQTT G/W

Hi Dwarka Thanks for the pointer. Any ideas which iotivity release contained that? Why was it dropped from subsequent releases? On Tue, Aug 21, 2018 at 5:16 AM, Dwarkaprasad Dayama < dwarka.day...@samsung.com> wrote: > 3 years ago MQTT code based on Protocol Plugin Manager (PPM) existed. > > Bu

Re: [dev] MQTT G/W

This is of course need to be investigated. For a start I think of having the MQTT broker handle all OCF security as currently implemented in iotivity code. For MQTT part, I am not an expert, so I can start assuming the client just publish without constraints. On Mon, Aug 20, 2018 at 10:52 PM, Mats

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 c

Re: [dev] Major issues with connecting to cloud using TLS

> the "secure resource" is just an (insecure) file which it wouldn't be on a > real device What should be used on a real device? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9886): https://lists.iotivity.org/g/iotivity-dev/message/9886 Mute Thi