Thank you for the clarifications Mr.Choi. Will definitely wait for new plugin management design on Twiki.
Thanks and Best Regards, N Ravi ------- Original Message ------- Sender : Uze Choi<uzchoi at samsung.com> S6/Principal Engineer/IoT Solution Lab./Samsung Electronics Date : Jun 03, 2015 16:18 (GMT+05:30) 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: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] 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
