Hi Jay, JungYoung, Dynamically setting Discoverable flag looks common use case, I think. >From the resource directory, it could be used also, which disable the multicast channel instead of undiscoverable setting.
Habib, could you check the use case from your side for this new API usage from RD also? Jungyoung, you can consider the disable the multicast channel as the additional action from the ?RH delegation request device? as like current RD implementation. BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Friday, January 15, 2016 8:08 AM To: ???; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Proposal: explicit method for start of Resource Hosting Hello Junghyun. You are right. IoTivity Stack does not provide APIs for update resource policy. However IoTivity Stack already has functionality for update policy dynamically. (e.g. OCChangeResourceProperty() ocstack.c) So, I think if we needs to change of resource policy, we can make API easy. When review of this proposal is done, I will propose to make API for update resource policy. Regards, JungYong ------- Original Message ------- Sender : ???<junghyun.oh at samsung.com> S5(??)/??/IoT Lab(S/W??)/???? Date : 2016-01-14 18:29 (GMT+09:00) Title : RE: [dev] Proposal: explicit method for start of Resource Hosting Hi To my understanding, IoTivity Stack does not provide any APIs for updating the resource policy(such as discoverable or observable). Could provide us ?How the application could update the resource policy dynamically?? (ex Discoverable a Non-discoverable) Thank you. Jay. From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Thursday, January 14, 2016 5:42 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Proposal: explicit method for start of Resource Hosting Hello All. As you know, Resource Hosting(RH) already located on iotivity primitive services. RH is useful service for reduction of thin device's power consumption. But, start of RH has a problem, so I propose an explicit method for start of RH to improve it. Please check attached a proposal. As is, if thin device want to reduce power consumption, thin device can implicit requests to RH. This is very simple and easy way. But, thin device should watch for creation of hosting resource. If thin device can explicit requests, thin device should find RH, but thin device can know about creation of hosting resource. I think the latter is more clear method for start of RH. Please review and feedback this proposal. Regards, JungYong. <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=213efb02e5f841dc8b7685e a07ddb076b4de788d285322b87a1cde04f48a2130be7dd83ce6b932973c40f787d33f357d4b3 1597edd603a7ce5a22f09e2218feaa728c55b39cc59eacf878f9a26ce15a0> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160115/0703bddc/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/20160115/0703bddc/attachment.gif>
