Currently OC_ALL is valid only for multicast discovery and not for the unicast case (reason being the underlying CA APIs that is called for OC_ALL works only for multicast address).
--Vijay From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Monday, June 01, 2015 1:16 AM To: Kesavan, Vijay S; Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org Subject: [OC_ALL defect for unicast discovery and presence] : API does not work properly after CA code change Hi Vijay/Pat OC_ALL is still problem for unicast discovery and presence with subscribePresence() API. Temporarily we are switching the code OC_ALL into OC_IPv4 which causes the code maintenance issue. Previous commit https://gerrit.iotivity.org/gerrit/922 is valid only for specific connectivity but not applicable to OC_ALL. Could you share the plan to support it? According to your answer, I?ll decide the code submit whether we change it (OC_ALL --> OC_IPv4 --> OC_ALL) or wait your bugfixing. BR, Uze Choi From: Kesavan, Vijay S [mailto:vijay.s.kesa...@intel.com] Sent: Thursday, May 07, 2015 10:55 AM To: uzchoi at samsung.com<mailto:uzchoi at samsung.com> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: API does not work properly after CA code change Uze ? the OC APIs have not been modified in this changeset to remove the distinction between Ethernet and WiFi. We are working on that and expect a separate changeset in the near future. --Vijay From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Kesavan, Vijay S Sent: Wednesday, May 06, 2015 6:36 PM To: uzchoi at samsung.com<mailto:uzchoi at samsung.com> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] API does not work properly after CA code change Uze ? please check https://gerrit.iotivity.org/gerrit/922 This is a workaround for the presence issue. Unicast discovery is working OK for us. Regards, --Vijay From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Wednesday, May 06, 2015 4:25 PM To: Kesavan, Vijay S Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; '???'; '???'; '???'; '???'; '???'; h.marappa at samsung.com<mailto:h.marappa at samsung.com> Subject: RE: API does not work properly after CA code change Vijay, That?s Great. Please notify when fixed. And share the API change also. Furthermore, are you aware that OC_ALL makes crash? Now, We have a workaround way remedy on the all services code. BR, Uze Choi From: Kesavan, Vijay S [mailto:vijay.s.kesa...@intel.com] Sent: Wednesday, May 06, 2015 8:16 PM To: uzchoi at samsung.com<mailto:uzchoi at samsung.com> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; ???; ???; ???; ???; ???; h.marappa at samsung.com<mailto:h.marappa at samsung.com> Subject: RE: API does not work properly after CA code change We came across this issue as well and are investigating it. Please stay tuned for an update on it. Thanks, --Vijay From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Wednesday, May 06, 2015 1:33 AM To: Kesavan, Vijay S Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; ???; ???; ???; ???; ???; h.marappa at samsung.com<mailto:h.marappa at samsung.com> Subject: API does not work properly after CA code change Hi Vijay, After WiFi and Ethernet connectivity are merged together in the CA, Presence and unicast discovery feature is not working now.(Lastest master branch) Due to this error, WE cannot develop the feature right now. And, Could you share the API change from the RI(Resource Introspection) by unifying WiFi and Ethernet connectivity. OC_WIFI and OC_ETHERNET are not valid anymore and OC_ALL is not working either. I need to prepare the primitive service code change according to the base layer API change. BR, UZe Choi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150602/abd53120/attachment.html>
