The choice of "OC_IPV4" is mistaken and temporary. It will soon be OC_IP, with the address family inferred.
John Light Intel OTC OIC Development -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Tuesday, May 19, 2015 4:57 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] How to use an unicast discovery for Arduino device with WiFi shield? On Tuesday 19 May 2015 23:10:36 Samidurai, Sakthivel wrote: > You should able to call findResource with ?coap::// ip > address:6298/oc/core?rt=core.light? and OC_IPV4 parameters For > example, findResource (??, ?coap::// ip > address:6298/oc/core?rt=core.light?, OC_IPV4, &foundResource); This means this API has redundant parameters. If the IP in the URL is IPv4, why does one have to specify OC_IPV4 again? Do we have an OC_AUTO or something? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
