Gabriel, I will add my own clarification. IoTivity is a communications framework defining a client and server. The server talks to sensors and actuators on the same machine as it resides. The client talks to remote servers. So the client indirectly talks to the sensors and actuators on a remote network node running the server software.
John Light Intel OTC OIC Development -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Schulhof, Gabriel Sent: Friday, May 08, 2015 2:22 AM To: Balaji N Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Physical Sensor -- Device Driver code Hey! Being an absolute newcomer to iotivity myself, I'm sure I will be corrected by the authorities on this project. I will attempt an explanation in the hope that in doing so I expose my own lack of knowledge, to be corrected by those who know better :) It is my understanding that iotivity is not about talking to sensors that are present on the same device on which iotivity itself is running. iotivity is about making information from physical sensors accessible remotely via a well-structured, well-specified, well-known protocol. Thus, you write your own code to talk to the sensor, and then you create a resource using OCCreateResource. iotivity then calls the entity handler for the resource. The entity handler contains requests which have arrived from a remote location asking about the nature of the sensor, the capabilities of the sensor, and also possibly containing commands to be written to the sensor. So, in server mode, iotivity allows you to provide a unified interface for remote access to sensors. Its strength is that you don't have to write the networking code for accepting remote requests yourself. Please, authoritative persons, correct me where I'm wrong :) HTH, Gabriel _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
