JungYong,
There was a request from the ?IoTivity Simulator? developer to share the plan for such API. I was kind of negative on the idea to extend the APIs without reasonable use-cases for it. However, I think it would be nice to have if the use-cases where this ?Resource-Hosting? feature could be utilized are reasonable & practical enough. But still, we need to consider the side-effect that this new APIs would bring to the Resource Client. Here is the question.. - Q1. What happens if a Resource Client has discovered this Resource Server before it(Server) register himself to the ?Resource Hosting(RH)? manager? Case 1. If the resource server response back for the request from the Resource Client ==> the benefit of having RH will be minimized. Case 2. If the resource server does not react for the request from the Resource Client after registering to the RH ==> the service of Resource Client would fail. - Suggestion1. Your Proposal + Make Resource Server not Discoverable until it fails to discover the RH within reasonable time, then make himself to discoverable. (However, this would influence the QoS of the Resource Server since it could not provide its service until it changes to ?Discoverable? state) - ? Any other thoughts? Thank you. Jay. From: ??? [mailto:[email protected]] Sent: Friday, January 15, 2016 8:08 AM To: ???; iotivity-dev at lists.iotivity.org Subject: Re: 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 <mailto: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 * Non-discoverable) Thank you. Jay. From: [email protected] <mailto:iotivity-dev- bounces at lists.iotivity.org> [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 <mailto: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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160115/47c63276/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160115/47c63276/attachment.gif>
