On 06/20/2016 08:53 PM, Annie Weng wrote: > Hi All: > > Our team is now studying the resource hosing service. > > But it seems that the behavior of the sample code (for Linux) doesn?t match > the flow diagram of RH?s wiki page > (https://wiki.iotivity.org/resource_hosting). > > According to the flow diagram, there should be 3 main steps: > > 1. RH server create RH resource. > 2. Original server find and publsh its resource to RH. > 3. Original server disable its discoverable property. > > But we didn?t find corresponding behaviors in RH?s sample code. > > It seems that the sample code go with a different flow. > > Could someone help us about the correspondence between the Linux sample code > and the RH?s flow diagram?
I wouldn't make too many assumptions about samples. Generally speaking, resource hosting (resource directory - are there other situations involved?) should mean a device has delegated another to respond on its behalf for activities like discovery, so it doesn't have to stay awake to respond to multicasts for that purpose; the resource always has a URI which means it can be talked to directly when it matters. What do you see in the samples that doesn't match this? (I don't know what's in the samples you looked at, this is simply a question of "please elaborate")
