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

Timeout? #47

Open
KammutierSpule opened this issue Nov 21, 2023 · 3 comments
Open

Timeout? #47

KammutierSpule opened this issue Nov 21, 2023 · 3 comments

Comments

@KammutierSpule
Copy link

Does it make sense to add a timeout capabilities ?

Or is possible to implement some flush/reset of the internal state?

@marcinbor85
Copy link
Owner

Hi. Tnx for the question. What is the real use case of such feature? What would You like to achieve?

@KammutierSpule
Copy link
Author

KammutierSpule commented Nov 22, 2023

I'm wondering on cases with disruption in the lines. Are there mechanisms to recover?
Other cases: the other side hang or crashed.

@marcinbor85
Copy link
Owner

marcinbor85 commented Nov 22, 2023

Which side of the communication channel should retry after timeout? Master/Host/Server (cAT - which basically send responses only) or slave/client (external device with app which send requests and WAIT for responses)?

Slave/Client side is responsible for ensuring that the cAT is in the "ready" state. Its very easy to achieve just by sending "\n" or "AT\n" and waiting for response. In both cases its job for Slave/Client app, not for cAT library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants