Hi Max, Your understanding is correct. There is ongoing work to remove the IoTivity limitation you mention below, but it is not in the 1.3 branch. The AllJoyn bridge uses multiple processes and the resource directory to comply with the bridging spec.
-Todd On Tue, 2017-07-25 at 23:24 +0300, Max Kholmyansky wrote: Hi, I wonder if and how IoTivity 1.3.0 provides a support for building bridge devices compliant with the OCF 1.0 Bridging Specification. Speaking technically: which APIs are available in order to register under IoTivity platform multiple bridged devices (with unique "di") and their respective resources, in a way that /oic/res (resource discovery) will return a packet as described in the "Spec". The AllJoyn bridge page (https://github.com/iotivity/iotivity-alljoyn-bridge) says: "Currently the bridge requires multiple processes to manage multiple instances of IoTivity (one per bridged AllJoyn device). " Is it an IoTivity limitation? The bridging page in the Wiki - https://wiki.iotivity.org/bridging_project - provides the following option: This scheme is much like the first one, except you can host more than one OIC Smart Home device type in a single instance of IoTivity. You set the device type of your instance of IoTivity to "oic.d.bridge". Then you represent each device you want to host as a collection resource. Each collection that you create that has a device type (i.e. "oic.d.*") in the array of resource types is recognized as a device. Each collection recognized as a device binds the associated resources within it. (Use "bindResource" API for this.) But if I got it right, this does not fit OCF 1.0, and even within OIC 1.1 - OCF clients need to implement the logic in the code of treating such a collection resource as a logical "device" - nothing in the infrastructure supports this convention. Correct me if I am wrong on this. Thanks and best regards, Max _______________________________________________ iotivity-dev mailing list [email protected]<mailto:[email protected]> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
