Re: [dev] Proposed API guidelines

2018-01-03 Thread Philippe Coval
On 03/01/18 23:44, Gregg Reynolds wrote: > > > On Wed, Jan 3, 2018 at 3:49 PM, Dave Thaler > wrote: > > Below > >   > > *From:* Gregg Reynolds [mailto:d...@mobileink.com > ] > *Sent:* Tuesday, January 2, 2018 9:46 PM >

Re: [dev] Proposed API guidelines

2018-01-03 Thread Gregg Reynolds
On Wed, Jan 3, 2018 at 4:43 PM, Dave Thaler wrote: > Gregg wrote: > > We have branches for this kind of stuff. General rule: nothing goes into a > release that is not production-quality and officially supported. Otherwise > what is the point of having releases at all, instead of mere tags? > > >

Re: [dev] Proposed API guidelines

2018-01-03 Thread Dave Thaler via iotivity-dev
Two more proposed guidelines: § All new Public C/C++ API names must start with “OC” § All public headers must follow IoTivity Coding Standards. Comments on those? Dave From: Dave Thaler Sent: Wednesday, January 3, 2018 2:43 PM To: 'Nash, G

Re: [dev] Proposed API guidelines

2018-01-03 Thread Gregg Reynolds
On Wed, Jan 3, 2018 at 3:49 PM, Dave Thaler wrote: > Below > > > > *From:* Gregg Reynolds [mailto:d...@mobileink.com] > *Sent:* Tuesday, January 2, 2018 9:46 PM > *To:* Dave Thaler > *Cc:* iotivity-dev > *Subject:* Re: [dev] Proposed API guidelines > > > > > > > > On Aug 18, 2017 10:55 AM, "Dav

Re: [dev] Proposed API guidelines

2018-01-03 Thread Dave Thaler via iotivity-dev
Gregg wrote: We have branches for this kind of stuff. General rule: nothing goes into a release that is not production-quality and officially supported. Otherwise what is the point of having releases at all, instead of mere tags? [DT] The master vs. separate-branch discussion is certainly releva

Re: [dev] Proposed API guidelines

2018-01-03 Thread Gregg Reynolds
On Wed, Jan 3, 2018 at 3:36 PM, Nash, George wrote: > > The whole concept of "experimental API" makes little sense to me. > "Release with experimental (i.e. non-production) APIs" strikes me as an > oxymoron. > > > > > We have branches for this kind of stuff. General rule: nothing goes into > a re

Re: [dev] Proposed API guidelines

2018-01-03 Thread Dave Thaler via iotivity-dev
Below From: Gregg Reynolds [mailto:d...@mobileink.com] Sent: Tuesday, January 2, 2018 9:46 PM To: Dave Thaler Cc: iotivity-dev Subject: Re: [dev] Proposed API guidelines On Aug 18, 2017 10:55 AM, "Dave Thaler via iotivity-dev" mailto:iotivity-dev@lists.iotivity.org>> wrote: As the new API ma

Re: [dev] Proposed API guidelines

2018-01-03 Thread Dave Thaler via iotivity-dev
Below From: Gregg Reynolds [mailto:d...@mobileink.com] Sent: Tuesday, January 2, 2018 9:17 PM To: Dave Thaler Cc: iotivity-dev Subject: Re: [dev] Proposed API guidelines On Jan 2, 2018 7:18 PM, "Dave Thaler via iotivity-dev" mailto:iotivity-dev@lists.iotivity.org>> wrote: Two new proposed AP

Re: [dev] Proposed API guidelines

2018-01-03 Thread Nash, George
> The whole concept of "experimental API" makes little sense to me. "Release > with experimental (i.e. non-production) APIs" strikes me as an oxymoron. > We have branches for this kind of stuff. General rule: nothing goes into a > release that is not production-quality and officially supported.

Re: [dev] Question about IP adapter variation according to TARGET OS

2018-01-03 Thread Ashok Babu Channa
In Tizen, there is permission issue and device need to be rooted to use netlink APIs and Android, I don’t remember exactly but WIFI manger provided better events. Regards, Ashok From: Gregg Reynolds [mailto:d...@mobileink.com] Sent: Wednesday, January 03, 2018 11:22 AM To: Ashok Babu Chann