On Feb 24, 2017 1:19 PM, "Dave Thaler via iotivity-dev" < iotivity-dev at lists.iotivity.org> wrote:
As platform support project architect/maintainer, I am calling the question? I have previously heard arguments on this list for dropping Arduino support in IoTivity itself, which I will summarize as: 1) IoTivity-constrained is designed for this use case and should be used instead 2) Some code paths have not been maintained for some time 3) There is no IoTivity submaintainer for Arduino I have not yet heard arguments to keep it. So the question is: should we drop Arduino support in IoTivity and instead refer Arduino developers to IoTivity-constrained? yes, but no. we should drop support for the sdk in question, but not for Arduino per se. "Iotivity does not support Arduino" sends the wrong message. It does support Arduino (101 at least), using iotivity-constrained. It's partially a messaging/marketing issue, imo. gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170224/932d0a00/attachment.html>
