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 -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160517/8d710555/attachment.html>
