Wez Furlong 58d969e77c gui: Avoid 450ms delay on startup(!) ... In the case that the published symlink is stale, our default client connection logic was to retry connecting with backoff to give a newly spawned server a chance to startup. In the context of a newly launched gui process checking to see if an existing gui process can serve the same request, we don't need to give it any grace: it will either answer immediately or be deemed not useful. This commit limits us to a single connection attempt in the case where we're not automatically starting the server, which in turn constrains the overhead to something in the order of microseconds rather than nearly 0.5 seconds. While we're in here, I noticed that if we thought we had a socket to try and that failed, we'd always try to publish a new symlink. However, if we failed due to mismatched version info, we shouldn't publish over the top of the already running instance. refs: #1529		2022-01-10 20:31:01 -07:00
..
src	gui: Avoid 450ms delay on startup(!)	2022-01-10 20:31:01 -07:00
Cargo.toml	gui/client: add stubs for publishing a main gui instance sock path	2022-01-06 20:07:46 -07:00