Hi Pawel,
My name is Jay and am working on utilizing iotivity for several home appliance
products.
Unfortunately, I have used this depth-3 arrays for some features on those
products already
and about to get certification test sooner or later.
For the back-ward compatibility issue, those APIs related with this depth-3
array thing is required.
Here is the example how I am utilizing this feature on those products.
Request : GET /Resource_X
Response : {
?n? : ?Array Items?,
<=== 1 - depth
?x.com <http://x.com/>.mycompany.Items? : [
<=== Array property
{
<=== 2 - depth
?id? : 1,
?actions? : {
?value" : true
<=== 3 - depth
},
?targets? : [
?oic.r.switch.binary"
],
},
{
<=== 2 - depth
?id? : 1,
?actions? : {
?modes" :
?hello_world? <=== 3 - depth
},
?targets? : [
?oic.r.mode"
],
},
?..
]
}
I would like to say ? I do agree that we may have better way of supporting
depth-3 array like features
on the iotivity?, however, I think we need to consider deprecating existing
APIs more carefully because of the
backward compatibility support.
Thank you.
Jay.
> 2017. 2. 11. ?? 10:00, Pawel Winogrodzki via iotivity-dev <iotivity-dev at
> lists.iotivity.org> ??:
>
> Hi all,
>
> Recently I?ve stumbled on an issue regarding the ?AttributeValue? type, which
> is a boost::variant with 26 types in its template.
>
> This makes the compiler truncate the symbol name (under Windows the compiler
> shows the C4503 warning
> <https://msdn.microsoft.com/en-us/library/074af4b6.aspx>), because it exceeds
> 4096 characters. Not only may that cause linking issues, but also makes
> debugging a lot harder.
>
> I?ve looked at the code and it seems that part of that variant (depth 3
> arrays) is not used anywhere except for the tests and my suggestion is to
> remove it, until it?s actually needed. I?ve verified, that this would fix the
> issue and here?s my code change suggestion, so you can see what changes are
> required: https://gerrit.iotivity.org/gerrit/#/c/17195/
> <https://gerrit.iotivity.org/gerrit/#/c/17195/>.
>
> Please let me know, what are your suggestions.
>
> Pawel
> _______________________________________________
> iotivity-dev 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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170215/f9f360f5/attachment.html>
