Currently High maps to confirmable and all else is non-confirmable.
Agree, QoS might not be the right term and as a part of API update we will look
into it.
--Vijay
-Original Message-
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On
Qos is defined as High, Med, and Low , which maps to confirmable and
non-confirmable.
I?ve seen no guidance in the documentation as to what Med is supposed to
really mean.
Qos usually implies throughput, latency, etc. Is QoS really a good term
for this?
What does Med imply?
Somewhat of an issue with passing arbitrary binary data is that we are
dealing with JSON, which will require conversion to escaped ASCII anyway
(or some odd B64 solution).
The OCRepresentation changes for a new type (uint8_t) are pretty
trivial, however the JSON serialization will require quite a
The thought here is that std::string is already a collection of 'char',
and a single-length string is a single char.
I'm curious to see what others have to say, so perhaps this is something
that could be added anyway.
If you push a review to Gerrit, I'd definitely be willing to review and
consi
Current iotivity doesn't support char datatype which makes
transmitting binary data difficult.
Will char datatype be support in the future?
diff --git a/resource/include/OCRepresentation.h
b/resource/include/OCRepresentation.h
index ef9d1a9..434286b 100644
--- a/resource/include/OCRepresentation.
vity.org/gerrit/#/c/811/3
Bill.
------ next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150428/ba679675/attachment.html>
Thank you, Thiago, for pointing that out.
I will add that many robust, well-written C/C++ programs don't set O_NONBLOCK
yet never block, through careful use of select.
John
-Original Message-
From: Macieira, Thiago
Sent: Monday, April 27, 2015 5:00 PM
To: iotivity-dev at lists.iotivity
On Tuesday 28 April 2015 11:09:49 Keane, Erich wrote:
> Somewhat of an issue with passing arbitrary binary data is that we are
> dealing with JSON, which will require conversion to escaped ASCII anyway
> (or some odd B64 solution).
Right, it needs to be encoded with base64url.
> The OCRepresentat
Hi,
Why don?t we have the C API docs on the web site next to the C++ API docs
(https://api-docs.iotivity.org/0.9.0/index.html) ?
Sakari
From: , Joseph L mailto:joseph.l.mor...@intel.com>>
Date: Thursday, April 23, 2015 at 20:58
To: "Dieter, William R" mailto:william.r.dieter
at intel.com>>, "
On Tuesday 28 April 2015 16:45:28 Keane, Erich wrote:
> The thought here is that std::string is already a collection of 'char',
> and a single-length string is a single char.
>
> I'm curious to see what others have to say, so perhaps this is something
> that could be added anyway.
>
> If you pu
Hi Bernie,
If your commit works well then please go ahead (submit).
Primitive Service point of view, we are making the additional commit for
each service to align with updated Android base layer code.
Our commits will have the dependency on your "834" commit.
BR, Uze Choi
-Original Message---
On Tuesday 28 April 2015 01:39:47 Jon A. Cruz wrote:
> On 04/28/2015 01:06 AM, Han-Lin Li wrote:
> > Current iotivity doesn't support char datatype which makes
> > transmitting binary data difficult.
> >
> > Will char datatype be support in the future?
>
> Just a minor note:
>
> For a binary dat
On Tuesday 28 April 2015 07:33:39 Light, John J wrote:
> Thank you, Thiago, for pointing that out.
>
> I will add that many robust, well-written C/C++ programs don't set
> O_NONBLOCK yet never block, through careful use of select.
That is true, though I still advise using O_NONBLOCK.
The one cas
Hi Uze,
Thanks for the reply, we?ll go ahead and submit to master for review
beginning tomorrow. We?ll let you know as soon as it is there for review.
BR,
Bernie
On 4/27/15, 6:22 PM, "???(Uze Choi)" wrote:
>Hi Bernie,
>
>If your commit works well then please go ahead (submit).
>Primitive Servi
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150428/0e5f4f4a/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201504281122569_04A24XEV.gif
Type: image/gif
Size: 13168 bytes
Des
On 04/28/2015 01:06 AM, Han-Lin Li wrote:
> Current iotivity doesn't support char datatype which makes
> transmitting binary data difficult.
>
> Will char datatype be support in the future?
>
Just a minor note:
For a binary data type I'd more expect to see std::vector
rather than std::vector.
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150428/623b94a0/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201504281010213_QKNMBDIF.gif
Type: image/gif
Size: 13168 bytes
Des
17 matches
Mail list logo
