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

Different apparatus checking flow #12

Open
jonahweissman opened this issue Feb 8, 2022 · 0 comments
Open

Different apparatus checking flow #12

jonahweissman opened this issue Feb 8, 2022 · 0 comments

Comments

@jonahweissman
Copy link
Member

Notes from my meeting with Dan.

Changes to be implemented:

  • new request type get_component_list returns names and types of every component
  • acquire_lock no longer requires arguments, clients should only call this if they have verified their compatibility with the component list

Advantages of this flow over the currently implemented one:

  • clients are insensitive to hardware specific changes (e.g. interrupt lines)
  • clients can be insensitive to extra components that they don't use
  • clients can be designed that can handle any configuration of components, like a web dashboard
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonahweissman