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

Dynamic supervision #9

Open
4 tasks
vertexclique opened this issue Jul 22, 2019 · 1 comment
Open
4 tasks

Dynamic supervision #9

vertexclique opened this issue Jul 22, 2019 · 1 comment
Labels
A-supervisor Area: Supervisor related issues C-feature-request Category: Feature Request

Comments

@vertexclique
Copy link
Member

  • looking for impls out there
  • message queue impl to take over the replacements
  • replacement syntax and definition of replacement conditions
  • complete branch migration
@vertexclique vertexclique added enhancement New feature or request research We need to take a look if this thing is possible labels Jul 22, 2019
@vertexclique vertexclique added the help wanted Extra attention is needed label Aug 31, 2019
@vertexclique
Copy link
Member Author

Dynamically spawned supervisors and processes should be available. futures should able to run a supervisor and place them under the tree.

@vertexclique vertexclique added this to the Runtime migration milestone Oct 15, 2019
@vertexclique vertexclique added this to Needs triage in Project Board via automation Oct 15, 2019
@r3v2d0g r3v2d0g removed their assignment Dec 20, 2019
@r3v2d0g r3v2d0g added A-supervisor Area: Supervisor related issues C-feature-request Category: Feature Request and removed enhancement New feature or request help wanted Extra attention is needed research We need to take a look if this thing is possible labels Dec 20, 2019
rtyler added a commit to rtyler/otto that referenced this issue Jan 5, 2020
I think I am going to have to abandon this approach for a couple of different
reasons:

 * Bastion does not yet support dynamic supervision
   <bastion-rs/bastion#9>
   This means that any workers which might handle websocket or other connections
   cannot possibly scale because the server would need to start with a fixed number
   of children under supervision. Contrary to what we have with actix-web where
   we use an actor per connection.

 * Tide/tungstenite do not yet integrate. It seems that actix-web and _maybe_
   gotham are the only two web frameworks which properly upgrade HTTP
   connections to websockets without requiring two fundamentally different servers
   to be running.
@vertexclique vertexclique moved this from Needs triage to High priority in Project Board Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-supervisor Area: Supervisor related issues C-feature-request Category: Feature Request
Projects
Project Board
  
High priority
Development

No branches or pull requests

2 participants