Complicating the issue in the current code base is that a network address in the second field is processed approximately the doc says the first argument is processed. However, I am changing that behavior as part of the IPv6 dev since the currently canned IPv4 address is not generally useful there.
I could fix the JIRA bug I submitted in my branch, but then it won't get to master for some time. John From: Keane, Erich Sent: Wednesday, February 25, 2015 10:53 AM To: Light, John J; iotivity-dev at lists.iotivity.org Subject: RE: Host field ignored in findResource It is likely a bug that we're ignoring a field like that. I'll note that all of platform/wrappers seem to ignore the first component to that or don't do the broadcast check. From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Light, John J Sent: Wednesday, February 25, 2015 10:48 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Host field ignored in findResource I submitted a JIRA on this, but I'd like a timely answer since it affects IPv6 work. The first argument to Platform::findResource (and Platform::findDevice) is ignored when the code reaches InProcClientWrapper::ListenForResource (or ListenForDevice). The field can be a host url, but documentation says an empty/null value is treated as broadcast, which is certainly the most common usage. Is this an oversight, a true bug, or intentional? Perhaps the field is being removed? John Light -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150225/3b0df42d/attachment.html>
