I think API work should be waaay beyond the current scope you defined. Current Cpp/Java APIs for example lacks basic OO design principles, which makes IoTivity very hard to integrate with other systems or even build a system from scratch without having to write lots of "feature wrappers".
regards, On Wed, May 3, 2017 at 3:52 PM, Gregg Reynolds <dev at mobileink.com> wrote: > > > On May 3, 2017 1:17 PM, "LaBrecque, Margaret" < > margaret.labrecque at intel.com> wrote: > > Hi, > > > > John Park, the OCF Exec Dir, requested a list of IoTivity areas which need > contribution in order to facilitate the OCF Board?s (and others?) request > for new contributors. > > > > We started a Google Sheet to compile areas where IoTivity needs > contribution. We also assigned Mentors that will help new contributors. > > > > I think everyone should be able to edit this Sheet: > > > > https://docs.google.com/spreadsheets/d/1d9gMVeepN8mbHUNHAudb > XSF2zpN4eg0_A1DJdocf-b8/edit?usp=sharing > > > suggestion: add "componentization". example: provisioning mgr uses > sqlite. there are many alternatives like LMDB https://en.m.wikipedia. > org/wiki/Lightning_Memory-Mapped_Database. Ideally, we would have a PM > API that would make it easy to adapt other dbs. iow, we should move to > treating iotivity as a toolset that vendors can use to build tools that are > differentiated but still support the standard protocol and data model. > > g > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > -- *Thiago Guedes Cunha de Moura* Graduando em Ci?ncia da Computa??o Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro Preto cel.: (31)99484-9864 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170503/886c3209/attachment.html>
