[dev] API Naming convention for IoTivity

2015-02-09 Thread Lankswert, Patrick
rubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150209/9ad1076c/attachment.p7s>

[dev] API Naming convention for IoTivity

2015-02-09 Thread Keane, Erich
On Mon, 2015-02-09 at 13:32 -0800, Thiago Macieira wrote: > On Monday 09 February 2015 13:30:02 Keane, Erich wrote: > > > a) the "lite", base C API > > > > /resource/csdk/stack/include/ocstack.h > > > > > b) the resources (discovery & connectivity) C++ API > > > > /resource/include/OCApi.h > >

[dev] API Naming convention for IoTivity

2015-02-09 Thread Keane, Erich
On Mon, 2015-02-09 at 13:24 -0800, Thiago Macieira wrote: > On Monday 09 February 2015 13:09:01 Keane, Erich wrote: > > On Mon, 2015-02-09 at 13:04 -0800, Thiago Macieira wrote: > > > 1) is this user-visible API? If not, then choose whatever and it doesn't > > > matter. > > > > We don't intend th

[dev] API Naming convention for IoTivity

2015-02-09 Thread Keane, Erich
On Mon, 2015-02-09 at 13:04 -0800, Thiago Macieira wrote: > On Monday 09 February 2015 20:58:37 Keane, Erich wrote: > > Ioty for C is great, however what do we wish to do with the CA API? It > > is currently using the CA prefix. Do we wish to double those up, > > eliminate them entirely, or repla

[dev] API Naming convention for IoTivity

2015-02-09 Thread Keane, Erich
Ioty for C is great, however what do we wish to do with the CA API? It is currently using the CA prefix. Do we wish to double those up, eliminate them entirely, or replace with Ioty? For the includes, are we saying the include directory should now be formed like: "/resource/csdk/include/iotivity

[dev] API Naming convention for IoTivity

2015-02-09 Thread Lankswert, Patrick
list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150209/163de5b8/attachment.p7s>

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread Maloor, Kishen
Geoffroy, That is something I didn?t know you could do - pretty cool :) I will test this out and update the recipe upstream. Thank You! -Kishen. On 2/9/15, 11:02 AM, "VanCutsem, Geoffroy" wrote: >Hi Kishen, > >> -Original Message- >> From: Maloor, Kishen >> Sent: Monday, February 09,

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread VanCutsem, Geoffroy
Hi Kishen, > -Original Message- > From: Maloor, Kishen > Sent: Monday, February 09, 2015 7:18 PM > To: Lankswert, Patrick; VanCutsem, Geoffroy; Prasad, Sudarshan; iotivity- > dev at lists.iotivity.org; Keany, Bernie > Subject: Re: [dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic) > > G

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread Maloor, Kishen
Geoffroy, The Iotivity recipe uses Yocto?s scons class and requires that scons be present in your Yocto build sysroot. The Yocto project comes with two recipes (python-scons and python-scons-native) which set this up for you. Unfortunately, this wasn?t a documented fact by the Yocto Project but I

[dev] some comments on CA

2015-02-09 Thread Xu, Martin
t -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150209/52ed315c/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 b

[dev] Android Base API usage guide and design sync request

2015-02-09 Thread 최우제(Uze Choi)
ity-dev/attachments/20150209/84447b88/attachment.html>

[dev] Breakage with transport codes

2015-02-09 Thread Morrow, Joseph L
Hi Jon, Thank you for your input. I have logged a Jira ticket for this issue (https://jira.iotivity.org/browse/IOT-319) & posted in the review for the new libcoap-18 that is being used in the Connectivity Abstraction (CA) branch (https://gerrit.iotivity.org/gerrit/#/c/189/1/resource/csdk/connec

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread Lankswert, Patrick
-- > Intel Corporation NV/SA > Kings Square, Veldkant 31 > 2550 Kontich > RPM (Bruxelles) 0415.497.718. > Citibank, Brussels, account 570/1031255/09 > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150209/6aede294/attachment.p7s>

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread VanCutsem, Geoffroy
Thanks Sudarshan and Patrick for your answers. I have seen the wiki pages on wiki.iotivity.org but the code (well, it's _just_ the recipe actually) that needs patching is in meta-oic which is hosted on the yoctoproject.org website. It is not clear to me if that means the bug should be filed on

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread Lankswert, Patrick
-- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150209/be1f200e/attachment.p7s>

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread Prasad, Sudarshan
Hi Geoffroy, Thanks for fixing the bug. This link has set of instructions for development workflow -- https://wiki.iotivity.org/. Specifically, to submit a change -- https://wiki.iotivity.org/submitting_to_gerrit If you want to create a bug or look for the same, we use JIRA -- https://jira

[dev] API Naming convention for IoTivity

2015-02-09 Thread Thiago Macieira
On Monday 09 February 2015 14:07:31 Jon A. Cruz wrote: > From some of my experience, using > > #include "iotivity/ocstack.h" > #include "iotivity/Api.h" > > is better than > > #include "iotivity/ocstack.h" > #include "iotivity/OCApi.h" > > > It can help with setting up different libraries with

[dev] API Naming convention for IoTivity

2015-02-09 Thread Jon A. Cruz
On 02/09/2015 01:41 PM, Thiago Macieira wrote: > On Monday 09 February 2015 13:36:53 Keane, Erich wrote: >> On Mon, 2015-02-09 at 13:32 -0800, Thiago Macieira wrote: >> >>> On Monday 09 February 2015 13:30:02 Keane, Erich wrote: >>> [SNIP] Unsure, but It looks like: /service//sdk/inc

[dev] API Naming convention for IoTivity

2015-02-09 Thread Thiago Macieira
On Monday 09 February 2015 13:36:53 Keane, Erich wrote: > On Mon, 2015-02-09 at 13:32 -0800, Thiago Macieira wrote: > > > On Monday 09 February 2015 13:30:02 Keane, Erich wrote: > > > > > > a) the "lite", base C API > > > > > > > > > /resource/csdk/stack/include/ocstack.h > > > > > > > > > >

[dev] API Naming convention for IoTivity

2015-02-09 Thread Thiago Macieira
On Monday 09 February 2015 13:30:02 Keane, Erich wrote: > > a) the "lite", base C API > > /resource/csdk/stack/include/ocstack.h > > > b) the resources (discovery & connectivity) C++ API > > /resource/include/OCApi.h > > > c) a specific service > > Unsure, but It looks like: > /service//sdk/in

[dev] API Naming convention for IoTivity

2015-02-09 Thread Thiago Macieira
On Monday 09 February 2015 13:09:01 Keane, Erich wrote: > On Mon, 2015-02-09 at 13:04 -0800, Thiago Macieira wrote: > > 1) is this user-visible API? If not, then choose whatever and it doesn't > > matter. > > We don't intend them to use it, however it IS C, so it is in the global > namespace. Ad

[dev] API Naming convention for IoTivity

2015-02-09 Thread Thiago Macieira
On Monday 09 February 2015 20:58:37 Keane, Erich wrote: > Ioty for C is great, however what do we wish to do with the CA API? It > is currently using the CA prefix. Do we wish to double those up, > eliminate them entirely, or replace with Ioty? Let me ask a few questions so we make a decision:

[dev] Bug in the iotivity_0.9.0.bb recipe (meta-oic)

2015-02-09 Thread VanCutsem, Geoffroy
Hi, I was trying to build IoTivity for Edison by following the README in http://git.yoctoproject.org/cgit/cgit.cgi/meta-oic/tree/README?h=master. I was initially facing an issue because 'scons' was not available in the sysroot (see [2] for the log output). This can easily be fixed by the follow

[dev] some comments on CA

2015-02-09 Thread Thiago Macieira
On Monday 09 February 2015 18:11:43 Xu, Martin wrote: > So as to select the connectivity, at most situation, I think we should let > IoTivity as well as the platform to pick the proper connectivity technology > according to the performance and connectivity status of the platform. If > you have some