Thanks for looking into it! I currently am pretty busy with the CBOR conversion, however anyone who wishes to submit a patch for this would be greatly welcomed.
Otherwise, I'll look into it when I get a chance. -Erich On Wed, 2015-07-08 at 08:33 +0000, ??? wrote: > Hi. Erich, > > > > Meanwhile, I found which function should be modified for right > operation of constructResourceObject(). > > In the second contructer of OCResource class with a parameter of > *std::string host*, some information which should be stored in > m_devAddr structure are wrong and missed. > > For example, as a parameter, host variable is passed like > "coap://10.0.2.15:36943" and should be properly parsed and stored to > m_devAddr structure. The following is the step for this: > > 1. Remove "coap://" prefix. > > 2. IP address without port number is stored to m_devAddr.addr > > 3. port number is stored to m_devAddr.port > > > > If do, constructResourceObject() would work well. Please look into > this. > > > > BR, Jihun Ha. > > > > ------- Original Message ------- > > Sender : ???<jihun.ha at samsung.com> S5(??)/??/IoT Solution > Lab(S/W??)/???? > > Date : 2015-07-08 10:30 (GMT+09:00) > > Title : Re: [dev] constructResourceObject() function does not work > well > > > > I think I use properly use parameters like host and uri for > constructResourceObject() function. > > host and uri parameters look like coap://10.0.2.15:36943 and /oic/con, > respectively. > > > > Please check it. You can examine the function with fridgeclient and > fridgeserver sample applications. > > > > ------- Original Message ------- > > Sender : Keane, Erich<erich.keane at intel.com> > > Date : 2015-07-08 01:34 (GMT+09:00) > > Title : Re: Re: [dev] constructResourceObject() function does not work > well > > > > The important part is the Host string's format. John Light can better > explain what that should look like, but if you do a resource.host() > call, you should see exact examples of what the format should look > like. > > > On Tue, 2015-07-07 at 10:54 +0000, ??? wrote: > > Hi. Erich, > > > > > > > > Even your patch has been merged, it looks that the problem may still > > exist. > > > > If you fix the problem, could you provide a way how to use > > constructResourceObject() function such as parameters? > > > > This could be help me to figure out if the problem can be resolved. > > > > > > > > Thank you. > > > > > > > > BR, Jihun Ha. > > > > > > > > ------- Original Message ------- > > > > Sender : Keane, Erich > > > > Date : 2015-07-02 01:25 (GMT+09:00) > > > > Title : Re: [dev] constructResourceObject() function does not work > > well > > > > > > > > I just pushed a review that should fix this (1430). Let me know if > > that > > fixes it for you. > > > > Thanks, > > Erich > > > > > > On Tue, 2015-06-30 at 16:32 +0000, Keane, Erich wrote: > > > Yep, we're still working through the review process on a > workaround > > and > > > trying to decide if it is the right fix. I'll respond to this > > thread > > > when we have something. > > > > > > Thanks, > > > Erich > > > > > > > > > On Tue, 2015-06-30 at 01:06 +0000, ??? wrote: > > > > Hi. Erich, > > > > > > > > > > > > > > > > What's going on the changes for contructResourceObject()? Any > > commit > > > > for this has not been merged yet. > > > > > > > > Please inform me if it is done. > > > > > > > > > > > > > > > > Thank you. > > > > > > > > > > > > > > > > BR, Jihun Ha. > > > > > > > > > > > > > > > > ------- Original Message ------- > > > > > > > > Sender : Keane, Erich > > > > > > > > Date : 2015-06-26 06:52 (GMT+09:00) > > > > > > > > Title : Re: [dev] constructResourceObject() function does not > work > > > > well > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ?????. ??? ??. > > > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > ?????. ??? ??. > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > ?????. ??? ??. > > > > 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 > > > > > > > > ?????. ??? ??. > > > > 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 > > > > > > >
