-
Notifications
You must be signed in to change notification settings - Fork 423
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
Save as we go #1243
Comments
julien-duponchelle
added a commit
to GNS3/gns3-server
that referenced
this issue
Jun 14, 2016
julien-duponchelle
added a commit
that referenced
this issue
Jun 14, 2016
julien-duponchelle
added a commit
to GNS3/gns3-server
that referenced
this issue
Jun 14, 2016
julien-duponchelle
added a commit
to GNS3/gns3-server
that referenced
this issue
Jun 15, 2016
julien-duponchelle
added a commit
that referenced
this issue
Jun 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kind of the same as #1028. We should move to a model where users don't need to save a project anymore, just like Google Docs. We can still allow to create a copy of a project but save as and save would be gone.
The main motivation is that it is difficult to synchronize what happens inside VMs with the GNS3 project state. For instance, an user deletes a node in GNS3, the server cannot really delete the VM in the back-end until the user saves the project, if the PC or GNS3 crashes or the GUI loose the connection with the server then the project is a inconsistent state. There is currently a "commit system" on the server side to handle some of the cases but this comes with complexity and it is not perfect.
The text was updated successfully, but these errors were encountered: