Hi JiHwan, I think this is good feature to users. Then should we open all functions to user or hide something to user? I found Java JNI specific around 10 APIs there. Can we separate split them? Furthermore, we should open cacommon.h file for data type used in cautilinterface.h.
BR, Uze Choi From: JiHwan Seo [mailto:[email protected]] Sent: Friday, March 24, 2017 3:55 PM To: Mats Wichmann; Uze Choi; ASHOKBABU CHANNA; 'Nash, George'; 'C.J. Collier' Cc: 'IoTivity Developer List' Subject: RE: Re: [dev] IoTivity documentation standards Hi Uze and Mats. Since there were so many requirements to handle CA layer in person. I believe that this header can be helpped for lots of scenarios. please refer below the patchset https://gerrit.iotivity.org/gerrit/#/c/18157/ BR Jihwan --------- Original Message --------- Sender : Mats Wichmann <mats at wichmann.us> Date : 2017-03-23 23:56 (GMT+9) Title : Re: [dev] IoTivity documentation standards On 03/23/2017 08:24 AM, ??? wrote: > Thanks Ashok. > Then cautilinterface.h also has lots of functions. > All are required open? This header has no @file section, is there a description of the purpose of the header available? _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/f6be6eb0/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13402 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/f6be6eb0/attachment.gif>
