[riot-notifications] [RIOT-OS/RIOT] tinydtls: add `sock_async` support for `sock_dtls` (#12907)

Martine Lenders notifications at github.com
Thu May 7 16:28:42 CEST 2020


> Yes, I agree. The blocking behavior can still be done even with `sock_async`. So that means `sock_dtls_send` will need to refer somewhere to decide to block or not. We could add a parameter `nonblock` to the function or set non-blocking per sock in `sock_dtls_create`.

How about keeping it symmetric to `recv` and making it a `timeout` where `0` is non-blocking and `SOCK_NO_TIMEOUT` is blocking? Something similar would then be needed for `sock_dtls_create_session()` as well (I was wondering why it isn't already anyway)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/12907#issuecomment-625289418
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200507/c80a9ff9/attachment.htm>


More information about the notifications mailing list