The RD server works as expected. The publishing client is not working
correctly. We had to modify the code to get it to work as expected.
However, the modified code is not generic enough to share to the community.
RD is just a directory very much like DNS about other nodes that exist in
the networ
Hello,
I have tried to use RD using the instructions here :
https://wiki.iotivity.org/resource_directory_-_programming_guide
I build using command scons resource/csdk/resource-directory/
RD_MODE=all and then
I start the RD server:
./rd_server
and I get in the console:
OCResourceDirectory
An architectural correction: the local OCF servers typically discover RD
and register with it not the other way around.
On Mon, Apr 16, 2018 at 3:37 PM, Khaled Elsayed
wrote:
> If the devices have public IP addresses (not recommended), they can be
> accessed with the help of a resource direct
If the devices have public IP addresses (not recommended), they can be
accessed with the help of a resource directory RD server. The RD should
perform local discovery of the devices and can share this information with
external end points.
If devices have non-routable addresses, then proxy+RD is t
On Sat, Apr 14, 2018, 8:51 AM Maria Koutli wrote:
> Hello all,
>
> Is there a way to access an IoTivity server outside of its local network
> (find resources, send get, post requests etc) without using the IoTivity
> Cloud architecture? If yes, could you point me to some
> documentation/example c
Hello all,
Is there a way to access an IoTivity server outside of its local network
(find resources, send get, post requests etc) without using the IoTivity
Cloud architecture? If yes, could you point me to some
documentation/example code?
Thank you.
Best Regards,
Koutli Maria
___
