I totally agree with the statements below.. But I do not want to diminish the work that has gone into IOTivity, because it does work! Also we should not try to replace IOTivity with a new project… it still should be named IOTivity but with better tools, documentation etc. One needs to be up and running code in just an hour or so…
My idea is to have an small core library with support of: - Implementation of mandatory resources (core + security) - Clean api to: o Register new resources - Build system that has an plug in system, e.g. if you want to compile your own application: that should be easy o I finally figured out how to build on windows after moaning on this email thread, it only took me 5 months to get going.. § Not sure if I move to another PC I will be up and running again in a few hours… o I could compile IOTivity constrained in just a few hours: just: make This enables an Code generator for application resources. The code generator can use support libraries if the logic gets complex.. Kind Regards, Wouter From: [email protected] [mailto:[email protected]] On Behalf Of Gregg Reynolds Sent: 07 December 2017 20:01 To: Dave Thaler <[email protected]> Cc: iotivity-dev <[email protected]> Subject: Re: [dev] which libcoap to use in master branch? On Dec 5, 2017 1:25 PM, "Dave Thaler via iotivity-dev" <[email protected]<mailto:[email protected]>> wrote: ... Iotivity should really be rewritten to be a clean layer on top of the normal libcoap APIs. +1000 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! 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. Actual documentation that is useful. A non-bonkers build system. 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!") Well I might do all that with OpenOCF but I am just one bear, of little brain. And I think Iotivity should do it. 2 cents, g
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
