Uze, With regards to your questions, as discussed previously, the first version of Iotivity with CA will support selecting the connection type in relevant APIs. Additionally, there will be support to distinguish the same resource discovered on multiple interfaces using a unique identifier, the server ID. These features along with sample applications are already implemented in the CA branch.
Yes, there are differences between the master and CA APIs (C & C++), not very extensive, and when CA is merged with master the APIs will need update. Early next week we will send an email to the reflector outlining the changes and actions that have to be taken by those using the APIs. On an unrelated but relevant note, perhaps you are following the discussion threads in the mailing list suggesting how to handle multiple interfaces. Some of the suggestion are reasonable and when incorporated are expected to result in additional API changes. Regards, --Vijay -----Original Message----- From: ???(Uze Choi) [mailto:[email protected]] Sent: Wednesday, March 18, 2015 8:54 PM To: Kesavan, Vijay S Cc: Lankswert, Patrick; iotivity-dev at lists.iotivity.org Subject: RE: [API change info sharing request] RE: Change in iotivity[master]: Redefine and implement findResource API Hi, Vijay Regarding the previous question, I haven't got the response yet. May I expect your explanation? First of all, please Let me clear there is any difference the base layer API between the master branch and connectivity abstraction branch. BR, Uze Choi -----Original Message----- From: ???(Uze Choi) [mailto:[email protected]] Sent: Friday, February 13, 2015 1:06 PM To: Kesavan, Vijay S (vijay.s.kesavan at intel.com) Cc: 'Patrick Lankswert'; iotivity-dev at lists.iotivity.org Subject: [API change info sharing request] RE: Change in iotivity[master]: Redefine and implement findResource API Hi Vijay, Could you share the Base Layer API change according to the CA layer merging? As far as I know, two feature were discussed. - connectivity selection - host parameter to identify the Resource Server/Clients are same one according to the different connectivity. And status together whether implemented or be planned. BR, Uze Choi -----Original Message----- From: Gerrit Code Review [mailto:[email protected]] Sent: Wednesday, February 11, 2015 2:52 AM To: Caiwen Zhang Cc: Uze Choi; Patrick Lankswert; jenkins-iotivity Subject: Change in iotivity[master]: Redefine and implement findResource API
