My understanding is that Olaf wanted the huge iotivity patch broken into lots of little patches, which never got done. So the reimplementation of coap-over-tcp by others exposed a slightly different API surface, and got accepted.
-----Original Message----- From: Mats Wichmann [mailto:[email protected]] Sent: Thursday, November 9, 2017 10:57 PM To: Dave Thaler <[email protected]>; [email protected] Subject: Re: [dev] FW: [core] Testing CoAP/TCP at the IETF100 Hackathon? On 11/09/2017 07:17 AM, Dave Thaler wrote: > Now that the master libcoap supports the latest COAP-over-TCP draft > (and other features we would want like FETCH/PATCH), I think what we > would need would be to update iotivity's use of libcoap to use the > master version rather than our fork which is missing features and > doesn't support the latest draft.\ I don't know the history behind the forks, was there something we needed that we could not get accepted by Olaf? I think I've rooted out the problems with Linux building the "upstream" (dthaler) fork so we should be good to go with experiments, at least. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
