Persistent Application Session

[Zubnix]

Currently when a user exits the compositor, all applications are destroyed. In theory it should be possible to persist all application/client related state to a database. This allows for resuming applications on login after the previous compositor has been destroyed (by ie browser exit). Another use case would be to detach a running application from one compositor and transfer it to another user's compositor in real-time.

[t123yh]

Thanks for your great work! I think this one is very critical for Greenfield to become a perfect remote working environment. We don't want to lose our work caused by Internet disruption or browser crash.

[cfouche3005]

Hi, any news on this feature ?
Greenfield is a great project, thank you for creating it but the non-persistent session is kind of a deal breaker for me and my use case.

[Zubnix]

Currently no effort has been made to make state survive a disconnect from the user. It should be doable and the architecture certainly allows for it but it would require some (not so mild) refactoring in the compositor code. The compositor code would need to be split in a server-side state keeping part, and a client side (browser) part used for viewing. This, this, this and the video decoding parts of this would somehow need to run in the browser, while everything else would run on the server.