I would use something instead of OC_NA_QOS, cause I don?t think that?s valid. Also if you run loop only calls OCProcess every 2 seconds , then things will be very slow.
Charlie Lenahan | Software Engineer | Intel Corporation | 322 West Main Street | Louisville, KY 40202 | W - 502.963.0917 | 8-963.0917 charlie.lenahan at intel.com | CDG ? WINS ? WSS EAST | http://www.linkedin.com/in/charlielenahan On 5/5/15, 6:54 AM, "Schulhof, Gabriel" <gabriel.schulhof at intel.com> wrote: >Hi! > >I'm trying to write a simple client/server pair in C using >OCCreateResouce on the server side and OCDoResource on the client side >to find the server. I'm not getting any communication between the two. >That is, neither the OCEntityHandler of the server is ever getting >called, nor is the OCClientResponseHandler on the client side ever >getting called. > >I've tried tracing the C++ examples >resource/csdk/stack/samples/linux/SimpleClientServer/occlient.cpp and >resource/csdk/stack/samples/linux/SimpleClientServer/ocserver.cpp to >see which C API calls they end up making, but they're a bit of an >eyeful, because they have lots of options in the way of tests. > >I've also looked at >https://www.iotivity.org/documentation/linux/programmers-guide/registering >-resource >and >https://www.iotivity.org/documentation/linux/programmers-guide/finding-res >ource >to see how the code shown there gets passed through to the C API. > >Could you please look over >https://gist.github.com/gabrielschulhof/c11f3f91fde92c61bde8 and let >me know what I'm doing wrong? > >I'm linking against master @ 4f0bfbea4c09efc13cbf4d768d0d9d8c87026e21 > >TIA for your help! > > > >Gabriel >_______________________________________________ >iotivity-dev mailing list >iotivity-dev at lists.iotivity.org >https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5859 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150505/bedf51aa/attachment.p7s>
