What we have there kinda works, but there are many issues that need improving/resolving:

• bandwidth: pulseaudio's TCP protocol is a bandwidth pig... We must ensure we only use it over fast links (need better detection?)

Edit: see original description for the approach that was abandoned (pure pulseaudio)

We should probably watch the output of the Xvnc process like we do for NX. Looks like we can detect if the session is connected or not: vncext: Listening for VNC connections on port 16064 Means no need to test using a wait_for_socket. Connections: accepted: 127.0.0.1::51920 Means we can remove the need for the client to set the CONNECTED status. Connections: closed: 127.0.0.1::51920 (Clean disconnection) As above for AVAILABLE.

Log Xvnc output to file ~/.Xvnc/:DISPLAY.log

Note: the code has only been tested with tigervnc...

Can't find the release notes, so I don't know how important this is..