Hi Gregg! First time I’ve seen that patch myself; it looks like it was dropped when Microsoft devs were reassigned off of IoTivity.
The only good news about this behavior is that IoTivity Lite is the recommended basis for products including power constrained Devices; at this point IoTivity is recommended only for proving feasibility of Specification (the OCF “3-pillar alignment” requirement of Specification, Implementation, and Certification). So I guess the answer to get rid of this polling loop is “use IoTivity Lite”. Though I admit I’m still familiarizing with the Lite stack, it is a much cleaner implementation, without the legacy and undue complexity of IoTivity. If you want to give it a try, check out the getting started page on IoTivity.org: https://iotivity.org/getting-started Thanks, Nathan From: [email protected] [mailto:[email protected]] On Behalf Of Gregg Reynolds Sent: Tuesday, December 11, 2018 2:47 PM To: iotivity-dev <[email protected]> Subject: [dev] Ocprocess polling Asking the app to poll ocprocess is obviously undesirable. Whatever happened to https://gerrit.iotivity.org/gerrit/#/c/18277/? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10074): https://lists.iotivity.org/g/iotivity-dev/message/10074 Mute This Topic: https://lists.iotivity.org/mt/28724461/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
