Hi Randeep,
Could you share your idea or progress for this requirement? BR, Uze Choi From: Madan Kanth Lanka [mailto:[email protected]] Sent: Thursday, May 26, 2016 2:30 PM To: Uze Choi; RANDEEP SINGH Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] [feature request] merging secure/non-secure IoTivity build binaries Hi Randeep, I also think the scenario requested by Uze is valid scenario. There is already a JIRA ticket reported during 1.0.0 release. https://jira.iotivity.org/browse/IOT-920 Thanks, Madan ------- Original Message ------- Sender : Uze Choi<uzchoi at samsung.com> S6/Principal Engineer/IoT Lab./Samsung Electronics Date : May 26, 2016 09:16 (GMT+05:30) Title : [dev] [feature request] merging secure/non-secure IoTivity build binaries Hi Randeep, As a member Developer Ecosystem Build TG, I have the requirement merging the non-secure binary and secure binary into single one. Currently, secure mode build does not provide the communication with non- secure resource. If this is configurable by API or both support by default, it will be very easy to distribute iotivity binary. Moreover, current separate build scheme cannot support the use case that connects both resources one is secure resource and the other is non-secure resource. e.g) An application read the temperature resource (public resource) and personal information storage resource together. Please evaluate this requirement from maintainer perspective. If feasible, I?ll issue the jira ticket for this thing. BR, Uze Choi -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160602/04596feb/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/20160602/04596feb/attachment.gif>
