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.

Sign up for GitHub

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

Jump to bottom

sdsRecInit/sdsPlayInit and sdsRecOpen/sdsPlayOpen behave differently depending on IO #80

Open
MiloradCvjetkovic opened this issue Mar 13, 2025 · 0 comments
Open

sdsRecInit/sdsPlayInit and sdsRecOpen/sdsPlayOpen behave differently depending on IO #80

MiloradCvjetkovic opened this issue Mar 13, 2025 · 0 comments
Labels
enhancement New feature or request sds-core Belongs to SDS-Framework/sds

Comments

@MiloradCvjetkovic
Copy link
Collaborator

sdsRecInit/sdsPlayInit and sdsRecOpen/sdsPlayOpen functions behave differently depending on IO.

If socket is used for IO and SDSIO-Server is not running, the sdsRecInit/sdsPlayInit will fail.
If USB (VCOM) is used for IO and SDSIO-Server is not running, the sdsRecOpen/sdsPlayOpen will fail.

This behavior could be unified in a way that, in both cases, if the SDSIO-Server is not running the sdsRecInit/sdsPlayInit would fail after a number of retries (to allow VCOM server to connect).

This would require adding a way to check if Server is up and running, like server ping functionality.
@MiloradCvjetkovic MiloradCvjetkovic added enhancement New feature or request sds-core Belongs to SDS-Framework/sds labels Mar 13, 2025
@MiloradCvjetkovic MiloradCvjetkovic moved this to Backlog in SDS Framework Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request sds-core Belongs to SDS-Framework/sds
Projects
SDS Framework
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MiloradCvjetkovic