On Tuesday, 5 December 2017 11:25:23 PST Dave Thaler via iotivity-dev wrote:
> The github libcoap is what we should try to use in the future, but they
> didn't accept iotivity's libcoap changes and instead made non-compatible
> changes so that it would require a bunch of iotivity work before we can
> actually use it. For example, it has an RFC-compliant COAP-over-TCP
> implementation that differs from the one that iotivity uses. And iotivity
> just uses libcoap to compose/parse packets, not for the business logic,
> which in my view is bad. Iotivity should really be rewritten to be a
> clean layer on top of the normal libcoap APIs. I don't expect that to
> happen any time soon though as I've not heard anyone signing up for
> significant work.
Do we know if the socket logic that IoTivity implements can be done with
libcoap?
This list may not be exhaustive, but we need:
1) 4 sockets: (unencrypted, encrypted) times (multicast, unicast)
2) ability to join the OCF multicast group, not the CoAP one
3) integration with the network monitor capabilities, like which interfaces
to whitelist or to blacklist
4) integration with our crypto library of choice, which now seems to be
mbedTLS, not tinydtls
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
