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

Multi-process / persistent applications #2

Open
mistasse opened this issue Nov 10, 2019 · 0 comments
Open

Multi-process / persistent applications #2

mistasse opened this issue Nov 10, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@mistasse
Copy link
Member

For now, only one thread handles all the applications running on a server. Different improvements would be enjoyable :

  • It would be convenient to have one thread per session
  • It would be convenient to be able to have a process having a webapp, that can modify its state and access its events. The user should be able to disconnect and reconnect and the process should just go on.
    To this end, the computing process could create a thread and a session with a local socket for sharing state and messages, no webserver.
    Another webserver thread could serve the client applications, collect inputs and forward them through the local socket

It seems to me that there is some overlap between those two improvements, and something to do about both at the same time.

@mistasse mistasse added the enhancement New feature or request label Nov 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant