Thank you for your note Jay. With regards to the questions/comments you raised:
Since we start discussion about the Connectivity-abstraction from last year, (What connectivity & How to support...) the concensus we've made was "This will be one of IoTivity's key features". Therefore, I think it is important to publish this feature asap, so that 3rd parties experience this advantage by actually use this CA feature on their app or services. I'm also waiting for this features to be added asap so that the we could improve primitive services & also extend new services based on CA feature. I really do appreciates your hard work & I'm really am sorry for pushing, however, I will be appreciated if you understand the how important this is to be published asap, not just for us(all the contributers of IoTivity) but also for the actually users. :) [Vijay]: We completely agree with you on the importance of CA. The teams working on CA development and integration have been ploughing hard at enabling the feature and have a working version on the CA branch. For those interested in previewing the CA feature, please check out CA 0.9.0 release branch from the repository. The teams are currently taking steps to integrate with master and as a part of this effort, there are a couple of Gerrit reviews (more to come next week) and here are the links (link1<https://gerrit.iotivity.org/gerrit/#/c/193>, link2<https://gerrit.iotivity.org/gerrit/#/c/189/>) for those interested in observing/participating. (Is it okey to contribute our code into the connectivity abstraction branch? 'cause the code changes for merging CA are happening in that branch..) [Vijay] If the code you wish to contribute related to the CA feature or the portion of the stack that integrates with CA, yes, it is OK to contribute code to the CA branch using the regular contribution process. Any other code should be added to master and we are regularly synchronizing CA branch with master. It will be nice if you inform us when if the schedule for merging finishs earlier or delays. [Vijay] Absolutely, we will post status updates to the mailing list. Regards, --Vijay ------- Original Message ------- Sender : Kesavan, Vijay S<vijay.s.kesavan at intel.com<mailto:vijay.s.kesavan at intel.com>> Date : 2015-01-20 21:52 (GMT+09:00) Title : RE: [dev] [Question] CA Feature Merge Releated 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: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<mailto: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 Jung-hyun Oh. IoT Solution Lab. | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD Mobile +82-10-9890-6731 | Beyond your imagination, Always 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 01D036C6.83056DE0] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=b65f9d91e1020aef4d17c91723ea4fc42ab2ad2b4ec5b307ed81201521b94ff84e60fcf6aeb61df594c3b6ddffd7613bcb238d00164b0be48eeb9bec5ad9c75d326bbdfb2ea96a2fcf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150123/0ee9540a/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/20150123/0ee9540a/attachment.gif>
