v mailing list
> iotivity-dev at lists.iotivity.org <mailto:iotivity-dev at lists.iotivity.org>
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
> <https://lists.iotivity.org/mailman/listinfo/iotivity-dev>
> <201502032128659_Z5JE7EUA.gif>
> ___
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150203/a17436eb/attachment.html>
On Tue, Feb 3, 2015 at 3:40 PM, Hudson, Douglas
wrote:
>> On Monday 02 February 2015 12:05:13 Jon A. Cruz wrote:
>> > > For C++, I think Iotivity:: is the correct namespace, but I'd
may we also get inspiration from DNS hierarchy and java
ie: use org::iotivity::lang use org::iotivity::utils
This
I like the ioty prefix for the C API. Upper or lower case? That is:
IotyDoResource
Or
iotyDoResource
I think I prefer the uppercase version (e.g. IotyDoResource) as it is
consistent with our current API names.
Doug
-Original Message-
From: Philippe Coval [mailto:philippe.co...@open
> On Monday 02 February 2015 12:05:13 Jon A. Cruz wrote:
> > > For C++, I think Iotivity:: is the correct namespace, but I'd
> > > remove the current OC prefix (that is what namespaces are for!).
Any thoughts on what we should do for the C API? I agree with a previous post
saying that prefixing
may I suggest ioty
prefix if iotivity is too long
My 2cents
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150203/3d4be738/attachment.html>
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150203/5527256b/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201502032128659_Z5JE7EUA.gif
Type: image/gif
Size: 13168 bytes
Des
If we set the name space as iotivity in Java/C++, removing the OC will be
the best option I think.
BR, Uze Choi
-Original Message-
From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-
bounces at lists.iotivity.org] On Behalf Of Keane, Erich
Sent: Tuesday, February 03, 2015 9
> -Original Message-
> From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-
> bounces at lists.iotivity.org] On Behalf Of Thiago Macieira
> Sent: Monday, February 02, 2015 8:57 PM
> To: iotivity-dev at lists.iotivity.org
> Subject: Re: [dev] API Naming convention for IoTiv
On Mon, 2015-02-02 at 16:46 -0800, Thiago Macieira wrote:
> On Monday 02 February 2015 12:05:13 Jon A. Cruz wrote:
> > > For C++, I think Iotivity:: is the correct namespace, but I'd remove the
> > > current OC prefix (that is what namespaces are for!).
> > >
> > >
> >
> > Again, I agree and drop