Hi KC, Thank you for your valuable advice. We?ll keep these in mind. Current redesigning is focusing on lightweight quality and abstraction of resource related implementation (easy to use from user) with same functionality as before. Please wait unveiling the update design on the IoTivity wiki page soon.
BR, Uze Choi From: ??? [mailto:[email protected]] Sent: Thursday, June 04, 2015 11:41 AM To: ???; RAVI NANJUNDAPPA; iotivity-dev at lists.iotivity.org Subject: Re: Re: [dev] reason for cpluff library inside protocol-plugin Hi all, Original PPM's target usage scenario was as follows. --------------------------------------------------------------------------- - Joe is using OIC application to control OIC light. - Joe has purchased non-OIC light like Philips Hue. - Joe searches and installs Hue plugin from the OIC web site. - After installing plugin, Hue light will be discovered dynamically as OIC device without restart of application. - Joe can control OIC light and Hue light with same OIC application. --------------------------------------------------------------------------- For this, PPM was based on OSGi framework because it provides basic dynamic component deployment model - install, update, start, stop, signing. However, recently, I also have some doubts on the reality about providing user level doployment model by IoTivity open source. In other words, it looks too much vertical solution for the open source. Anyway, protocol bridging itself is very necessary in current IoT area. I hope that "Resource Server Container" can be more generic, primitive and layered than PPM. Best Regards KC Park ------- Original Message ------- Sender : ???<uzchoi at samsung.com> S6(??)/??/IoT Solution Lab(S/W??)/???? Date : 2015-06-03 19:48 (GMT+09:00) Title : Re: [dev] reason for cpluff library inside protocol-plugin Hi Ravi, We have thought that this is protocol-plugin specific library and it will be also good to place this code into there. However, now we have redesign of PPM concept, to rename it as ?Resource Server Container? having dlopen logic instead of OSGi logic. This will not require no such as cpluff. I?ll share the new design soon on IoTivity WiKi. BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of RAVI NANJUNDAPPA Sent: Wednesday, June 03, 2015 6:40 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] reason for cpluff library inside protocol-plugin Hi All, Is there any reason why cpluff library is kept under service/protocol- plugin/lib dir ? I understand that its a plug-in framework for C Programs and may be suitable to keep inside the protocol-plugin dir. But isn't it a good idea to keep all the external libs under extlibs/ dir as other 3rd party library sources to maintain uniformity and consistency across Iotivity ? Thanks and Best Regards, N Ravi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150604/8e2f1405/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/20150604/8e2f1405/attachment.gif>
