You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to ask you about support of queue mode in current implementation of Wakaama. Is it currently supported?
I see that there is a mention about UQ mode in the implementation.
We have a following situation:
Let's say that after the COAP_MAX_TRANSMIT_TIME (93s) from the last ACK message sent from client to the server, we want to switch the client into SLEEP mode (SSL connection should be cancelled, registration persist).
Every request that the server sends to the client should be queued because the client is offline.
After some time, the client should be awaken to re-establish the connection with server (most probably the client will be awaken a few seconds before the registration/update).
There are two possible ways:
The client should perform full DTLS handshake for establish the connection.
The client should use session resumption for establishing the connection. (improvement in TLS handshake, quicker way)
After re-establishment of connection, the client should receive every request from server that was previously queued during the time when the client was in SLEEP mode.
The text was updated successfully, but these errors were encountered:
Hello,
I would like to ask you about support of queue mode in current implementation of Wakaama. Is it currently supported?
I see that there is a mention about UQ mode in the implementation.
We have a following situation:
Let's say that after the COAP_MAX_TRANSMIT_TIME (93s) from the last ACK message sent from client to the server, we want to switch the client into SLEEP mode (SSL connection should be cancelled, registration persist).
Every request that the server sends to the client should be queued because the client is offline.
After some time, the client should be awaken to re-establish the connection with server (most probably the client will be awaken a few seconds before the registration/update).
There are two possible ways:
After re-establishment of connection, the client should receive every request from server that was previously queued during the time when the client was in SLEEP mode.

The text was updated successfully, but these errors were encountered: