One of the biggest user-facing issues facing wayland adoption is robustness. A crash in the compositor can take down the entire session and lead to data loss.
With wayland being a constantly changing landscape and with more workload being put on the compositor process this doesn't seem to be going away.
This talk showcases work across multiple libraries and toolkits to tackle this at the root with a method of "compositor handoffs" allowing clients to safely securely and seamlessly reconnect to a relaunched wayland compositor. This not only tackles the issue of robustness but also opens up a whole avenue of new opportunities that were previously impossible; such as freezing and resuming applications.
We talk through the POC implementations made across multiple toolkits, and what changes are needed throughout wayland and mesa to support this.
|Code of Conduct||Yes|
|GSoC, EVoC or Outreachy||No|