support simultanious client connections

[ethanpailes]

Several people have brought up this feature as a nice thing to have. This could actually be somewhat tricky given shpool's existing architecture because of the way we have a per-session lock.

We may want to have a notion of readwrite sessions and readonly sessions the same way that abduco does.

[digitalsignalperson]

It's nice with e.g. screen multiple people can connect to the same session for troubleshooting / "CLI screenshare".

[ethanpailes]

Multiple people talking to the same shpool session may run into trouble because we currently protect against one user connecting to the daemon belonging to a different user to protect against priviledge escelation. I suppose we could add an off-by-default config option to allow this though.

[kflk]

What about the case of multiple cursors for live co-editing? You can see work by Zellij, Kitty, and Helix:

Share your Terminal with Multiple Cursors
https://zellij.dev/news/multiplayer-sessions/

Protocol extension: multiple cursors · Issue #720 · kovidgoyal/kitty
kovidgoyal/kitty#720

Something similar to VS Code Live Share · helix-editor/helix · Discussion #8568
helix-editor/helix#8568

[ethanpailes]

While supporting simultanious connections is a possibility for shpool, I don't think multiple cursors is in the cards. Merely mirroring sessions can be easily done in a shell-agnostic way, but multiple cursors would require knowing much more about how the inner shell works than shpool is able to know.