Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to respond if queried device does not have an active session? #138

Open
gmuratk opened this issue Apr 10, 2024 · 2 comments
Open

How to respond if queried device does not have an active session? #138

gmuratk opened this issue Apr 10, 2024 · 2 comments
Labels
enhancement New feature or request Spring25

Comments

@gmuratk
Copy link
Contributor

gmuratk commented Apr 10, 2024

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)

@gmuratk gmuratk added the enhancement New feature or request label Apr 10, 2024
@akoshunyadi
Copy link
Collaborator

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.

@gmuratk
Copy link
Contributor Author

gmuratk commented Apr 12, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Spring25
Projects
None yet
Development

No branches or pull requests

3 participants