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

feat(at_c): AtRpc implementation #413

Open
4 of 12 tasks
XavierChanth opened this issue Sep 30, 2024 · 0 comments
Open
4 of 12 tasks

feat(at_c): AtRpc implementation #413

XavierChanth opened this issue Sep 30, 2024 · 0 comments
Assignees

Comments

@XavierChanth
Copy link
Member

Client mode:

  • initialization
  • free
  • call

Server mode:

  • initialization
  • free
  • start

End2end test:

  • initialize server & verify params
  • initialize client & verify params
  • start server
  • call from client
  • figure out a way to ensure expect request is received by the server
  • ensure expected response

Considerations:

  • Can we continue avoiding the need to depend on pthread?
    • Most likely not as the client needs to poll for the response, or the implementation for the client's polling cannot reuse the server implementation like in dart
    • Can we wrap the pthread implementation to make it resilient to environment changes?
  • Should we allow the user to define structs to pass their custom requests or force them to pass a cJSON* ?
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

1 participant