To clarify using your syntax I?ve placed the components to a Hue Plugin in brackets ?[ ]?. The only part concerning a plugin is what is listed in brackets. [OCF Smart Home <-INSERT MAPPING LOGIC-> Hue Restful] <-> Hue Bridge (ZigBee HA1.2) <-> Hue Light Notice, I didn?t list MPM here. MPM just controls the lifecycle of a plugin (Load, Unload, Scan, Add, Remove, Reconnect) though usage of an IPC since each plugin is in a separate process. MPM does not start or control your plugin?s instance of IoTivity for you, the plugin is responsible for maintaining its own instance of IoTivity (we have optional helper code in a ?common? directory to help you if you?d like). MPM control path looks like following: MPM Library (Load, Unload, Scan, Add, Remove, Reconnect) <-> Plugin Thanks, Joey Morrow From: ??? (Uze Choi) [mailto:[email protected]] Sent: Tuesday, March 14, 2017 12:12 AM To: Morrow, Joseph L <joseph.l.morrow at intel.com>; Bell, Richard S <richard.s.bell at intel.com>; VanCutsem, Geoffroy <geoffroy.vancutsem at intel.com>; jihwan.seo at samsung.com; iotivity-dev at lists.iotivity.org Subject: RE: [dev] About miniPluginManager of bridging
Hi Morrow, Question from your answer. 2. The software component of the plugin contains the IoTivity instance. This same software component uses IoTivity APIs and Hue RestFUL APIs to bridge the two ecosystems within the same process. Each plugin instance gets its own IoTivity instance. Let me illustrate simple protocol model : MPM ? (IPC) -> Plugin ? (OCF CoAP) -> Bridge ? (Hue Restful) -> Hue_Light Is it correct? If not and ?MPM ? (IPC) -> Plugin ? (Hue Restful) -> Bridge ? (Hue Restful) -> Hue_Light? is valid, I don?t know why there is redundant module (bridge or plugin) to bridge two protocol. BR, Uze Choi From: Morrow, Joseph L [mailto:[email protected]] Sent: Tuesday, March 14, 2017 5:58 AM To: uzchoi at samsung.com<mailto:uzchoi at samsung.com>; Bell, Richard S; VanCutsem, Geoffroy; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging Hi Uze, We mentioned MPM is a replacement plugin framework for IoTivity. It doesn?t match the capabilities in any 1-to-1 way other than giving developers the tooling necessary to create a plugin. 1. Different device. 2. The software component of the plugin contains the IoTivity instance. This same software component uses IoTivity APIs and Hue RestFUL APIs to bridge the two ecosystems within the same process. Each plugin instance gets its own IoTivity instance. 3. Yes. Thanks, Joey Morrow From: ??? (Uze Choi) [mailto:[email protected]] Sent: Monday, March 13, 2017 1:19 AM To: Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>>; VanCutsem, Geoffroy <geoffroy.vancutsem at intel.com<mailto:geoffroy.vancutsem at intel.com>>; Morrow, Joseph L <joseph.l.morrow at intel.com<mailto:joseph.l.morrow at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging Hi Vijay/Joey, Good to see full documentation. Plugin sample code and loading plugin code will help the better understanding. You explained that MPM is replacement from Resource Container during F2F OSWG session, However, there are considerable gaps between them, let me ask followings include gap. 1) From your architecture, MPM, Hue plugin, Hue Bridge and Hue Light are listed. Hue bridge is also separate process in the same or different device? 2) Which node has a iotivity instance? Plugin looks having the IoTivity instance. And Hue Bridge should have it for discovery at least. Furthermore, Each plugin has its own IoTivity instance with separate Iotivity lifecycle or shares common iotivity instance? 3) Previous Resource Container has the interface class (BundleResource), it has request handler virtual method for GET/POST request. However, this concept has been removed, which means plugin developer should implement this function using IoTivity API by himself? BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Bell, Richard S Sent: Friday, March 10, 2017 7:18 PM To: VanCutsem, Geoffroy; Morrow, Joseph L; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] About miniPluginManager of bridging Geoffroy, Thanks that is better. They are now viewable? Thanks, -Rick Bell From: VanCutsem, Geoffroy Sent: Friday, March 10, 2017 11:12 AM To: Morrow, Joseph L <joseph.l.morrow at intel.com<mailto:joseph.l.morrow at intel.com>>; Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging I?ve updated the wiki page so that: 1. Both images are displayed full-size (instead of being scaled down to a 200-pixel width) 2. Clicking on them takes you directly to the full image in its own page Feel free to revert these changes if that?s not what you wanted to see. Geoffroy From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Morrow, Joseph L Sent: Thursday, March 9, 2017 8:24 PM To: Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] About miniPluginManager of bridging Hi Rick, You have to click on them, then that opens the attachment, then you click on it in that new page and this opens the image up fully. You will have to do that two times. I can?t find a way to add the image without this process. Thanks, Joey Morrow From: Bell, Richard S Sent: Thursday, March 9, 2017 11:05 AM To: Morrow, Joseph L <joseph.l.morrow at intel.com<mailto:joseph.l.morrow at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging Joey, Can you put those two images on separate wiki pages? I can?t really read them. Thanks, -Rick From: Morrow, Joseph L Sent: Thursday, March 9, 2017 7:29 PM To: Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging Hi Rick and JiHwan, I have gotten the diagrams updated and now they?re uploaded to the wiki. Please find them here: https://wiki.iotivity.org/bridging_project_architecture Thanks, Joey Morrow From: Bell, Richard S Sent: Wednesday, March 8, 2017 8:11 AM To: Morrow, Joseph L <joseph.l.morrow at intel.com<mailto:joseph.l.morrow at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging Joey, Thanks for support? -Rick From: Morrow, Joseph L Sent: Wednesday, March 8, 2017 5:09 PM To: Bell, Richard S <richard.s.bell at intel.com<mailto:richard.s.bell at intel.com>>; jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] About miniPluginManager of bridging Hi JiHwan and Rick, I am finalizing some architecture docs now. I will post these diagrams to the wiki and reply to this thread ASAP when they?re available. Thanks, Joey Morrow From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Bell, Richard S Sent: Wednesday, March 8, 2017 8:06 AM To: jihwan.seo at samsung.com<mailto:jihwan.seo at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] About miniPluginManager of bridging Hi, This what I have? MPM Documentation: https://wiki.iotivity.org/bridging_project * Infrastructure of a Plugin: https://wiki.iotivity.org/infrastructure_of_a_plugin o MPM infrastructure: https://wiki.iotivity.org/infrastructure_of_mpm Thanks, -Rick Bell From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of JiHwan Seo Sent: Wednesday, March 8, 2017 2:22 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] About miniPluginManager of bridging Hi All I can't find some document including Architecture, Sequence diagram. etc for miniPluginManager of Briding from wiki page. Anyone who know where can i find the document of miniPluginManager? [cid:image001.gif at 01D29CBC.37B7E8F0] [http://ext.samsung.net/mail/ext/v1/external/status/update?userid=jihwan.seo&do=bWFpbElEPTIwMTcwMzA4MTMyMTQyZXBjbXMxcDNmM2Q0MDUwZTM1MjMzMDJiZjg1NDljMTYwYmI2ZTU2ZCZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170314/e3ced7da/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13402 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170314/e3ced7da/attachment.gif>
