Jay - am taking the liberty of replying and Pat might add if I missed/misspoke anything. In the CA branch, as you note rightly, code in the resource model which integrates with the CA APIs is currently under the conditional flag CA_INT which is enabled by default. In preparation for merging CA branch to master we are working on the following items:
1. Ensure that all features working on master work on CA branch. 2. CA branch will be tested for WiFi and Ethernet interfaces (each interface separately and both interfaces enabled simultaneously) on Ubuntu. Arduino platform should support CA code on Ethernet and WiFi interfaces as well. 3. Clean up the CA integration code, i.e. remove CA_INT flag and address items flagged as "TODO-CA" in CA branch. 4. Review code related to CA and CA integration. We expect this process to continue till around mid-February. To your question on API changes, with introduction of CA, there will be base API changes (nothing drastic!) mainly to enable applications to specify the interface to send requests. As we get closer to merging to master, API change will be published in this mailing list so that affected components can take necessary action - stay tuned for details on this. Regards, --Vijay From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Monday, January 19, 2015 11:47 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] [Question] CA Feature Merge Releated Hi Pat, :) I have some questions regarding "CA" releted feature merge. Since we're expecting a release which is CA feature merged version at the end of this month, IoTivity Service Developers are plan to apply changed IoTivity Base APIs into their services. However, when I review the source code inside the Base, I found several #ifdef CA_INT code which handles the "CA" included build mode. The questions are 1. Are those code will be remained in the up-comming release or removed? (If it remains we also have to have that code inside, which we do not want it to be..) 2. Will there be more API changes in the Base before the up-comming release? If then when is it? FYI, we're planning to finish our updates before Tuesday, next week. Thanks in advance. Jay. Jung-hyun Oh. IoT Solution Lab. | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD Mobile +82-10-9890-6731 | Beyond your imagination, Always [cid:image001.gif at 01D0346A.8150FA90] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=b65f9d91e1020aefa5f44b78ec053a691f495f10576551ceed81201521b94ff84e60fcf6aeb61df594c3b6ddffd7613bcb238d00164b0be48eeb9bec5ad9c75d326bbdfb2ea96a2fcf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150120/5b9da7f3/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150120/5b9da7f3/attachment.gif>
