Hi > On Dec 5, 2017 1:25 PM, "Dave Thaler via iotivity-dev" > <iotivity-dev@lists.iotivity.org> wrote: > ... > Iotivity should really be rewritten to be a clean layer on top of the >normal libcoap APIs. > > +1000
I agree that IoTivity should use the normal libcoap. > Not just for coap, but because the code is pretty horrible in general. It's > no wonder Iotivity has not attracted more core devs. There's me and there's > Matt's. Maybe a few other non-corporate visionaries. :) - come out of the > closet if you're out there! Hi again :) > So here's a proposal for version 2: total rewrite. Sane APIs. Y'know, the > kind devs can actually use now, without spending 3 months figuring them out. So far, I only looked into the C++ APIs - Yeah, there are certain areas that could be improved. > Actual documentation that is useful. ... and up to date! That would also help with the previous point. > A non-bonkers build system. As long as the new build system is well supported by Yocto, I'm fine with changing it. > Fixed and limited scope (no more "hey we got this great idea for our products > so we're going to shove it into Iotivity no matter how dumb it is but we can > do that since we're a Big Corp., Nyah nyah!") +1 What scope do you have in mind? Best Regards Martin _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
