Hello,

I wonder if IoTivity libraries provide an efficient programming model for
discovering server resources, in case the list of the resources isn't known
in advance.

At the OCF spec level, to my best understanding, an OCF server responds to
/oic/res with a single packet, containing the reported resources' list.

However, when performing "resource discovery" with Java or C++ IoTivity
libraries, the response is mapped into a callback called per resource
discovered. So inside such a callback, I found no way to determine whether
additional callbacks will arrive, i.e. whether the client received all the
discoverable server resources.

So unless I know in advance which resources are expected to be reported,
the solution requires to put kind of a timer (for how long?) => a potential
performance issue.

I am aware of the option to perform multicast via a single API call, and
obtain resources from multiple servers. However, I am interested to know
per server when the process is over.

Anyone has a better solution? Something worth to improve in future versions?


Regards,

Max.
Software Architect - Tekoia Ltd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170219/f3ec4617/attachment.html>

Reply via email to