Server per namespace vs Server per session #423

If I understand correctly, the server components of tmux and psmux differs in that tmux starts a server process per namespace [SPN] (using -L or -S) which hosts multiple sessions, whereas psmux starts a server per session [SPS].

psmux's SPS model seems to make it considerably trickier (if not downright impossible) to implement cross-session-support for commands like move-window, swap-window, link-window and others, in , which AFAICT ties the lifetime of a window to the session that created it, instead of like in tmux, the server (namespace) that created it.

I cannot claim to be a cross-session command power user in any way so it is not a huge limitation, but this was an unexpected difference between the two projects, and there are also other consequences - like assigning an unique sequential session id within a namespace is trivial in SPN (just a global variable), but something that needs to be coordinated between processes in SPS, creating potential race conditions.

I just wanted to ask if there are reasons(TM) for going with SPS, or if you'd be willing to move to SPN instead at some point?