We are collecting them internally and will be published soon. Thanks, =Sam -----Original Message----- From: Lenahan, Charlie Sent: Wednesday, May 20, 2015 9:03 AM To: Samidurai, Sakthivel; Macieira, Thiago; iotivity-dev at lists.iotivity.org Subject: Re: [dev] How to use an unicast discovery for Arduino device with WiFi shield?
Is this list of cleanup items public somewhere (wiki)? On 5/19/15, 8:07 PM, "Samidurai, Sakthivel" <sakthivel.samidurai at intel.com> wrote: >The current API requires specifying OC_IPV4. I agree with you that this >API has redundant parameters. We have this API in our list of cleanup. >We do not have OC_AUTO but we have OC_ALL. >Thanks, >=Sam >-----Original Message----- >From: iotivity-dev-bounces at lists.iotivity.org >[mailto:iotivity-dev-bounces at lists.iotivity.org] 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 >_______________________________________________ >iotivity-dev mailing list >iotivity-dev at lists.iotivity.org >https://lists.iotivity.org/mailman/listinfo/iotivity-dev
