wprs:
* does audio by forwarding a pulseaudio/pipewire socket, but it doesn't work so well for remote networks. I'd like to do something better in the future.
* defaults to 60fps and can support significantly higher refresh rates, depend on your cpu and bandwidth.
* aims to be low latency but prioritizes quality and so requires a good cpu and network connection to be low latency
* should be able to handle (possibly with some additional code) any input devices wayland supports
wprs doesn't do its own rendering, it passes through already-drawn image buffers from applications on the server side to the local compositor on the client side, which then composits/renders them however it wishes to.
Yes. A wprs session is persistent on the server (currently a single session per user, we're going to support multiple sessions for a user when we get to it), so you can connect/reconnect from different client computers.
If you start the application in a local wprsc connecting to a local wprsd instead of in the local compositor directly, you can later connect to the session with a remote wprsc.
Locking the screen (the other subthread in here) is not applicable to this, applications are drawn wherever the wprsc is running and only one wprsc can be connected at a time.
x->w, ra->rs