Hauke, I answered inline. BR, Uze Choi
From: Hauke.Mehrtens at lantiq.com [mailto:[email protected]] Sent: Wednesday, October 14, 2015 2:39 AM To: uzchoi at samsung.com; iotivity-dev at lists.iotivity.org Subject: RE: [dev] IoTivity plugin to non OIC protocol Hi Uze, Thanks for the quick answer. I am used to changing APIs in IoTivity and I do not see a problem in that in the current state of development. Should one device behind a bridge be represented as one resource in OIC? I have a Smart Plug which can also measure the consumed power, should I create one resource which has one value to switch the plug and some other value in the same resource to return the measurement data? ? OIC bridge concept is representing non-oic device as OIC resource. So definitely we should place the OIC resource over there. However, resource container creates and handles this resource by some bundle configuration. Is there a plan to implement the bridge like it is defined in the ?OIC Smart Home Device Candidate Specification?? ? Until now we don?t have such a plan, However, this is very good idea to create the template for resource model of OIC Smart Home Device Candidate. Anyway We will consider about it. The current configuration model is a little inflexible, if you are planning to change it, it would be better if a plugin can define its own configuration format and then also has to parse it by itself or add own arbitrary attributes. ? Detail requirement will be very helpful. Hauke From: Uze Choi [mailto:[email protected]] Sent: Dienstag, 13. Oktober 2015 17:04 To: Mehrtens Hauke (LQKG BU AE PS SW); iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTivity plugin to non OIC protocol Hi Hauke, As you may know, Old Protocol Plugin Manager has been re-designed into Resource Container. >From this new concept, we only need to implement the protocol switching logic >which means that we don't need to do something additional work such as >IoTivity Framework initialization, messaging handling and so on. We only need >to concentrate on the protocol converion logic. Resource Container also provides some templates which are specialized for their purpose such as protocol coverting and so on. Anyway, you need to use this template for your protocol conversion. This week presumably IoTivity v1.0 will be released with more detail programming guide and sample. You can start looking the Hue plugin example. Please keep in touch with me if there is any question from your trial. Anyway, I'm so sorry about depricating the Protocol Plugin Manager module. Please understand our decision for better usuability from developer point of view. BR, Uze Choi ------- Original Message ------- Sender : Hauke.Mehrtens at lantiq.com <mailto:Hauke.Mehrtens at lantiq.com%3cHauke.Mehrtens at lantiq.com> <Hauke.Mehrtens at lantiq.com> Date : 2015-10-13 23:22 (GMT+09:00) Title : [dev] IoTivity plugin to non OIC protocol Hi, I want non IoTivity devices to talk to OIC devices and vice versa. The protocol my non OIC devices are using is currently not integrated in mainline IoTivity, but I also want to integrate with ZigBee in addition and others if they are available. With IoTivity 0.9.2 I created a protocol plugin with the code located here: service/protocol-plugin/ in addition I created a small plugin manager using this interface. In IoTivity 1.0.0RC3 this code was removed and I see a plugin directory for ZigBee in plugins/, but it looks like ZigBee is hard coded into the code, ?grep zigbee plugins/src/ -ri? returns many results, so it looks like I have to modify the plugin handler code to add my plugin. The commit messages removing service/protocol-plugin/ says that I should use ?Resource Container? now it has the same functionality as the old protocols plugin. What should I use to integrate my bridge to a non OIC protocol? I think none of these implementations implement the bridge like it is defined in the ?OIC Smart Home Device Candidate Specification? 0.9.9 section 8 ?OIC Smart Home Bridge Device?, which already solves some of the problems I had with my bridge and IoTivity 0.9.2. It would be nice if someone could help me, I think bridges are very important in the beginning to integrate all the old devices with IoTivity and the consumer can still use his old devices and buy new OIC based devices. If someone can only answer half of the question it would still help. ;-) Hauke Mehrtens Lantiq Beteiligungs-GmbH & Co.KG <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=cb027b4aba19c2dcc237718f1584c670557651e8d8425996bbdc285bf47ca36a14a26fc0c1bfd6475ac4d0601bb49ccf5296970253332b3707805447a154a46fcf878f9a26ce15a0> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151014/536199ec/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151014/536199ec/attachment.gif>
