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

Split executable in several co-processes #20

Open
dod38fr opened this issue May 13, 2018 · 0 comments
Open

Split executable in several co-processes #20

dod38fr opened this issue May 13, 2018 · 0 comments

Comments

@dod38fr
Copy link
Owner

dod38fr commented May 13, 2018

Following the advices of "The art of Unix programming", splitting cme and Config::Model in several co-processes may help people understand what's going on under the hoods:

  • the communication between processes is done with a text protocol (needs to be bi-directional)
  • the GUI is done first
  • Each backend can have its own process

The design of Config::Model is already done in 3 main parts:

  • The UI (graphical or not)
  • the core (the configuration tree)
  • the read/write backend

Currently these 3 parts run withing a monolithic process using an API which is not too complex so splitting there should not be too difficult.

The protocol between the process must have instruction to get and set values but also to queries the configuration tree for:

  • online help
  • element list
  • list or hash indexes
  • element info (type, value type and other parts from the model)

I'll refine this bug further as the idea matures

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

No branches or pull requests

1 participant