Hi, I am trying to understand how IoTivity treats TCP-based endpoints (coap+tcp, coaps+tcp) and how it is related to the cloud support of IoTivity.
Is it right that "coap+tcp" is supported as a communication mechanism in parallel to the UDP-based "coap", once the library is built using WITH_TCP=1? If this is true, what connectivity settings in IoTivity SDK should be set, in order to expose such an endpoint by and OCF server? To communicate with such an endpoint from an OCF client? Is it defined as "Platform" level, or upon resource registration / discovery, or both? Now, suppose I want to publish the server resources to the IoTivity cloud. I am looking at the main() method of "aircon_controlee.cpp" cloud sample, trying to understand how it works. First, I see the standard AirConditioner resources (binary switch, temperature) are registered in a "regular" (?) way, so they become accessible locally (via coap/coaps?). Then, I see the AirConditioner resource is being registered, and then published to the cloud using 'publishResourceToRD' method with TCP connectivity type. Normally, AirConditioner does not need this resource - does it represent the "device" for the cloud, and makes its "child" resources exposed to the cloud? Was it made to illustrate the "collection" concept, or is it necessary? Is it OK to register resource separately with the cloud? Thanks a lot, Max
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
