Skip to content
New issue

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

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

Already on GitHub? # to your account

Redesign the registry API #329

Open
pavel-kirienko opened this issue Mar 30, 2024 · 0 comments
Open

Redesign the registry API #329

pavel-kirienko opened this issue Mar 30, 2024 · 0 comments

Comments

@pavel-kirienko
Copy link
Member

The current design is too complex, and there is a sensible way to simplify it without losing any important functionality. The simpler callback-based design worked well in embedded applications, and I think we should try it on PyCyphal. The segregation between the different backends needs to go, allowing the user to manually load-store the registers at node startup/shutdown as needed, while the Registry core remains merely a simple dict of callables.

The automatic creation of persistent registers needs to be reconsidered also to address #309.

We also need to support load/store to/from YAML, which is to be invoked manually by the application at the opportune time rather than implicitly; see #249. The Sqlite integration is not worth keeping.

Similarly to YAML, there may be a load backend that loads the register values from the command line arguments; the environment variable backend should perhaps be built in a similar way.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant