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
There may be cases where the queried device for connectivity or roaming does not have an active session. An appropriate API response needs to be agreed to ensure same behavior by multiple API providers. Possible evolution
An error response may be returned with an appropriate message.
A success message with a dedicated property maybe used to indicate device is not online
For connectivity we have the response value NOT_CONNECTED.
For roaming status the last known status is returned. So if the device changes to roaming and then it will be switched off, then the expected result is roaming=true.
Thanks @akoshunyadi. I think it will be good to document the expected behavior for the roaming case. We probably want to avoid API consumers mistakenly rely on retrieve-roaming-status response to infer device's connectivity status.
Problem description
There may be cases where the queried device for connectivity or roaming does not have an active session. An appropriate API response needs to be agreed to ensure same behavior by multiple API providers.
Possible evolution
An error response may be returned with an appropriate message.
A success message with a dedicated property maybe used to indicate device is not online
Alternative solution
Additional context
see: camaraproject/Commonalities#127 (comment)
The text was updated successfully, but these errors were encountered: