[riot-notifications] [RIOT-OS/RIOT] sock_dtls: add timeout to sock_dtls_send and sock_dtls_session_create (#14043)
notifications at github.com
Wed May 13 16:20:51 CEST 2020
@miri64 commented on this pull request.
* @return 0 on success
- * @return -EAGAIN, if DTLS_HANDSHAKE_TIMEOUT is `0` and no data is available.
+ * @return -EAGAIN, if @p timeout is `0` and handshake started.
Again: the workflow for `async` and non-`async` should not differ in their core. If I call the functions in an order because I know I have to do it this way, or if they are called, because the events come in in that order, it shouldn't make a difference.
> Should we reject all non-handshake packets?
No, ideally they should be properly de-multiplexed, queued if need be. But I know, this is not easily possible with `tinydtls`. Let me think on this a bit.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications