Handshaking of unsupported versions
31 views
Skip to first unread message
Stephan P.
Dec 3, 2021, 4:15:39 AM12/3/21
to AlpineBits
From the AlpineBits documentation, a specific case for handshaking is not clear. Therefore I would like to ask you how you would handle it.
A server supports only version 2020-10.
A client asks the server if it supports version 2018-10.
So it sends a corresponding OTA_Ping:Handshaking request for the 2018-10 version.
According to you, what should the server reply if it does not support this version:
A) Normal success response, citing "action_OTA_Ping" as the only supported action.
B) Respond with an error.
Case A somehow makes little sense because this version is not actually supported, there is not a single meaningful action supported.
In case B, what error should be reported. It can't answer with "ERROR: unknown or missing action", because it supports the handshaking action.
Answer A might be the best compromise. How should the server then answer for versions that do not (yet) exist? What should it answer for a query of version 2026-10? Should it assume that future versions might have the same handshaking and then answer at risk with support for action "action_OTA_Ping"? For a query for a not existing version 2021-10 with an empty versions array?
Should he then in the above case (unsupported 2018-10 verison) also respond with an empty versions array.
From my point of view this is not clearly documented, what do you say?
Stephan
A server supports only version 2020-10.
A client asks the server if it supports version 2018-10.
So it sends a corresponding OTA_Ping:Handshaking request for the 2018-10 version.
According to you, what should the server reply if it does not support this version:
A) Normal success response, citing "action_OTA_Ping" as the only supported action.
B) Respond with an error.
Case A somehow makes little sense because this version is not actually supported, there is not a single meaningful action supported.
In case B, what error should be reported. It can't answer with "ERROR: unknown or missing action", because it supports the handshaking action.
Answer A might be the best compromise. How should the server then answer for versions that do not (yet) exist? What should it answer for a query of version 2026-10? Should it assume that future versions might have the same handshaking and then answer at risk with support for action "action_OTA_Ping"? For a query for a not existing version 2021-10 with an empty versions array?
Should he then in the above case (unsupported 2018-10 verison) also respond with an empty versions array.
From my point of view this is not clearly documented, what do you say?
Stephan
Reply all
Reply to author
Forward
0 new messages