Hi Uze: (Yes, it is the plugin directory. Sorry for the wrong wording.)
Thanks so much for the reply! I'll use ResourceContainer for Zigbee bridge. Best Regards, Annie _____ From: ???(Uze Choi) [mailto:[email protected]] Sent: Tuesday, May 17, 2016 10:49 AM To: 'Annie Weng'; iotivity-dev at lists.iotivity.org Subject: RE: [dev] Question about Plugin and ResourceContainer Hi, Annie, If you point Zigbee code in the plugin directory (not sub-project), technically it is possible. However, Resource Container has not been adopted because the requirement of Zigbee plugin was low performance device only manage to handle the IoTivity base C API. Resource container is built up on the IoTivity base C++ API. Functional perspective, resource container is the easiest way to implement the non-OIC device support. BR, Uze Choi From: [email protected] [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Annie Weng Sent: Tuesday, May 17, 2016 11:34 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Question about Plugin and ResourceContainer Hi All: I'm interesting in the similarity of Plugin and ResourceContainer. I could see that there is a sub-project "plugin" to support Zigbee. Since "plugin" is also a kind of "non-OIC device" bridge, is it suitable to implement the same behavior of Zigbee plugin by ResourceContainer? ResourceContainer seems to be more flexible for expanding. (Coding Language is not a matter.) Thank you. Best Regards, Annie -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160517/4a020e9e/attachment.html>
