3 ms·
Also, xpra and waypipe are developed with the intent of being used remotely. They do not have any zero-copy provisions to reduce latency and overhead on local-o
by easygenes 5y ago
Also, xpra and waypipe are developed with the intent of being used remotely. They do not have any zero-copy provisions to reduce latency and overhead on local-only applications, like you would get with at least the virtio_wl and WSLg approaches.
- thefr0g 5y agoI didn't know virtio_wl, it looks pretty neat. WSLg doesn't seem to have too much focus on sandboxing and only works on windows :(
- easygenes 5y agoWell, in the case of WSLg the sandbox is WSL itself (and you can spin up multiple different ones, though they'd hardly qualify as micro VMs). The only part that "only works on Windows" is the RDP client. The rest is specifically developed for Linux and open source. The backend is an extension of FreeRDP, so presumably the FreeRDP client would be just fine on Linux.
- thefr0g 5y ago> The only part that "only works on Windows" is the RDP client. Ah ok, I thought they have an X server running under windows, but apparently not. (Was that in some previous version? I remember reading that.) > so presumably the FreeRDP client would be just fine on Linux. Memory sharing would need support by the hypervisor I guess, that probably means hacking FreeRDP, rdp-wayland-backend and the hypervisor :\
- easygenes 5y agoI haven't really looked at this yet: https://github.com/microsoft/weston-mirror/tree/working/libweston/backend-rdp https://github.com/microsoft/weston-mirror/tree/working/libw... Edit: This is the most interesting commit: https://github.com/microsoft/weston-mirror/commit/f590a956c378eb2ab765d05cb2331386f19f8704 https://github.com/microsoft/weston-mirror/commit/f590a956c3... Search for "shared" and "gfxredir"