After further consideration and discussion, I believe that exposing the OCDevAddr at the C++ level for the first time wouldn't be the best idea. I'm thinking we'd be better off just making host return a valid, routable string in OCResource, then make OCResource properly hand that down, which should fix this up.
John Light has agreed to contribute a patch for this, so feel free to contact him if you wish to help or have a conflict. Thanks all! -Erich On Thu, 2015-06-25 at 18:01 +0000, Keane, Erich wrote: > The issue seems to be that the port isn't properly being set in the > constructResourceObject. Previously, this was included in the 'host' > string, but it seems that it isn't anymore, so we are attempting to > connect to an endpoint on port 0! > > It seems that we might need to re-imagine this function a little to be > more consistent with this change. > > The solution might be to take a OCDevAddr object as a parameter rather > than the 'host', since it seems to have superceded it. This would > require OCResource to make this accessible as well. This would also > have the added benefit of allowing interface selection. > > Let me think over a solution (or others, please contribute thoughts or > patches!), and I'll get this fixed when I get a chance. > > Thanks for finding this! > > -Erich > > > On Thu, 2015-06-25 at 16:21 +0000, Keane, Erich wrote: > > That has worked in the past, but I'm not sure if it has been since > > broken. If I get a chance today, I'll take a look. > > > > > > On Thu, 2015-06-25 at 11:13 +0000, ??? wrote: > > > Hi. All, > > > > > > > > > > > > I'm trying to use constructResourceObject() function to make temporal > > > OCResource object to send a GET request to a certain resource server. > > > > > > But it looks like that it does not work well. I've tested with > > > fridgeclient/fridgeserver sample applications, which fails. > > > > > > > > > > > > For instance, in fridgeclient application, it tries to create > > > OCResource object for leftdoor and send a GET request with the > > > OCResource object. But, the response does not come. > > > > > > > > > > > > Anyone who knows what the problem is? > > > > > > > > > > > > ?????. ??? ??. > > > > > > > > > > > > Best Regards, > > > > > > > > > > > > Jihun Ha (???/???, Ph.D.) > > > > > > IoT, IoTivity, OIC | IoT Solution Lab > > > > > > Software R&D Center | Samsung Electronics Co., Ltd > > > > > > Mobile +82 10 2533 7947 > > > > > > jihun.ha at samsung.com | jhha85 at gmail.com > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > 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 > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
