I'd like to mention not standard but IoTivity API. Considering use case, interface information is not required. e.g) compare the resource with previously connected or check the duplication and create resource object without discovery step by putting address. Moreover, IPv4 and other transport do not provide this information either, which mean eventually user should handle it case by case. If transport information is required, we can use the other API which provides it.
BR, Uze Choi -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Friday, July 15, 2016 11:55 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] OcResource->getHost() api gives a tricky host address in Android On sexta-feira, 15 de julho de 2016 11:34:58 PDT ???(Uze Choi) wrote: > Let me make it clear again. > From IoTivity API perspective, not only % char but also following > interface info should be removed. e.g) > coap://[fe80::dafe:e3ff:fe00:ebfa]:49593 No, that's incorrect. The % should be %25 and the interface name has to remain. -- 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
