Hi Dwarka, Not only these below topics but, we also need to consider the Security model. I agree this daemon model is big topic. But looks required for commercial smart device product.
BR, Uze Choi From: Dwarkaprasad Dayama [mailto:dwarka.day...@samsung.com] Sent: Thursday, February 04, 2016 12:12 PM To: '???(Uze Choi)' Cc: hj210.choi at samsung.com; 'Thiago Macieira'; iotivity- dev at lists.iotivity.org Subject: RE: [dev] Proposal: Support multiple applications on a single smartdevice regardless of connectivity type Dear Uze, Daemon model or out-of-proc will work but we also need mechanisim or API?s to make sure multiple Iotivity consumers per physical device work without any conflict. For an instance, Spec says to have unique ?pi? (platform identfier) property per physical device no matter how many logical devices it has. In the context of this email each logical device can be treated as an individual App. AFAIK Iotivity does not support such case. Regards Dwarka ---------------------------------------------------------------------------- ------ Software R&D Center | Software Platform Team | IoT Lab Open Interconnect Consortium - Open Source Work Group Member Iotivity Steering Group - Advisory Committee From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ???(Uze Choi) Sent: Thursday, February 04, 2016 11:51 AM To: hj210.choi at samsung.com; 'Thiago Macieira'; iotivity- dev at lists.iotivity.org Subject: Re: [dev] Proposal: Support multiple applications on a single smartdevice regardless of connectivity type Hyungjun, Let me classify your use case for each connectivity. IP connectivity (Wi-Fi/Eth) : multiple iotivity instance can exist work with different port. BT connectivity : multiple iotivity instance will make a collision together due to same UUID on RFComm. The multiple OIC BT application requires single iotivity instance which can aggregate the BT communication. For this requirement, daemon process model which was out-of-proc model defined before, is only solution I think. BR, Uze Choi From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Thursday, February 04, 2016 11:13 AM To: Thiago Macieira; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Proposal: Support multiple applications on a single smartdevice regardless of connectivity type >> I?m not sure that current IoTivity can support this requirement irrespective >> of connectivity type such as BLE. If not, I suggest it is time to discuss to >> make it possible on IoTivity to cope with market trend. > >Hello Hyungjun Hi Thiago > >I'm not sure what problem you see in the first place. For a client and a server >application to run on the same device, we simply need the client's discovery >packets to somehow discover the server that is running there. From that point >forward, everything should proceed normally with current code. > >All we need for this is to configure our multicast query packets to be sent >with IP_MULTICAST_LOOP / IPV6_MULTICAST_LOOP. > Thank you for taking the time to comment. Please let me clarify my previous email. I imagine that several client and several server applications run on the same smart device regardless of connectivity type especially IP and BLE. Please refer to file("Proposal_MultiAppSupport.pdf") which is attached this email. Kind Regards, Hyungjun. ------- Original Message ------- Sender : Thiago Macieira<thiago.macieira at intel.com> Date : 2016-02-04 03:26 (GMT+09:00) Title : Re: [dev] Proposal: Support multiple applications on a single smartdevice regardless of connectivity type On quarta-feira, 3 de fevereiro de 2016 06:46:58 PST Hyungjun Choi wrote: > Hi all, > > Let me propose an item for discussion that supporting multiple applications > on a single smart device regardless of connectivity type. > > In IoTivity, I think smart device (rich device) means smart phone, smart TV, > smart watch and other devices which can host multiple applications on it. > Let me assume that there is a smart watch which has sensors. It can provide > the measured information to other device as well as control another device. > > I think, it?s possible to imagine that provide those functionalities by > IoTivity to enrich its usability. In such case, it is necessary to operate > IoTivity client application and server application on a single > smart device simultaneously. Correct. > I?m not sure that current IoTivity can support this requirement irrespective > of connectivity type such as BLE. If not, I suggest it is time to discuss to > make it possible on IoTivity to cope with market trend. Hello Hyungjun I'm not sure what problem you see in the first place. For a client and a server application to run on the same device, we simply need the client's discovery packets to somehow discover the server that is running there. From that point forward, everything should proceed normally with current code. All we need for this is to configure our multicast query packets to be sent with IP_MULTICAST_LOOP / IPV6_MULTICAST_LOOP. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=c03cb6296d7f11883cad70b e01dbbc61464dba7d5850bc6a6644ab31040311a5be7dd83ce6b932973c40f787d33f357d4b3 1597edd603a7ce5a22f09e2218feaa728c55b39cc59eacf878f9a26ce15a0> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/f21cd93c/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/20160211/f21cd93c/attachment.gif>
