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

Implement connection scoped data #97

Closed
filippomc opened this issue Apr 25, 2020 · 0 comments · Fixed by #98
Closed

Implement connection scoped data #97

filippomc opened this issue Apr 25, 2020 · 0 comments · Fixed by #98

Comments

@filippomc
Copy link
Contributor

filippomc commented Apr 25, 2020

The retrieval of the runtime project should follow the same criteria of the Java backend. Every client connected receives its own id, bound to the websocket connection, so each connection can evolve the model separately.
Follow the new implementation with reconnect capabilities from openworm/org.geppetto.frontend#902.

High level design:
Geppetto backend high level design - Scoped managers and reconnect (1)

@filippomc filippomc transferred this issue from openworm/pygeppetto Apr 25, 2020
filippomc added a commit that referenced this issue Apr 25, 2020
filippomc added a commit that referenced this issue Apr 25, 2020
@filippomc filippomc mentioned this issue Apr 25, 2020
@filippomc filippomc linked a pull request Apr 25, 2020 that will close this issue
@filippomc filippomc moved this from Review to Release in Jupyter Geppetto roadmap Jun 18, 2020
@filippomc filippomc moved this from Release to Done in Jupyter Geppetto roadmap Jun 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

1 participant