Considering a constrained device with local sensor, if we treat sensor as resource, then it could be registered by registerResource(). Right?
If yes, then my understanding is it is application's task to find this sensor, read sensor data, answer resource querying/setting/observation request from IoTivity. IoTivity does not touch any part for physical sensor access. Is my understanding correct? Best regards, James -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago Macieira Sent: Friday, April 10, 2015 3:09 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Question about relationship between iotivity and sensord On Friday 10 April 2015 06:41:07 Li, Hao H wrote: > Hi, > > https://review.tizen.org/git/?p=platform/upstream/iotivity.git;a=summa > ry > https://review.tizen.org/git/?p=platform/core/system/sensord.git;a=sum > mary > > Iotivity has modules like soft-sensor-manager etc. > > Will Iotivity plan to integrate sensord to process sensor data? Or > they are designed to work independently and provide interface with > each other if needed? IoTivity doesn't read from sensors. However, it does provide API for reporting sensors over the network and for reading those reports. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
