Design Rudimentary Multi-Client Support

[iamrecursion]

Summary

It is important for our users that they are able to connect multiple IDE clients to a single running Enso project. This enables a multitude of sharing and collaborative workflows, letting users work seamlessly together from their own machines. While, initially, we only aim to have rudimentary multi-client support. we want to evolve to support collaborative real-time editing in the future, and so the implementation should account for this.

Furthermore, we want to remain compatible with the single-client LSP as we implement this, so care will need to be taken to ensure that we remain compatible while creating an authorisation flow for additional connections.

Value

We have rudimentary multi-client support in the engine, allowing multiple users to connect to one instance at once. Furthermore, maintiain LSP compatibility.

Specification

• Determine which portions of the LSP initialisation and authorisation flow need to be extended (if any) to support multiple client connections.
• Document any of these protocol extensions in the engine services design document.

Acceptance Criteria & Test Cases

• We can support multiple clients connecting to a single engine instance, where only one client is able to write at any given time.
• This functionality is rigorously tested using stub endpoints.