Overall this isn't wrong, but just to make a few corrections here... >its default is to send all your OpenGL operations to the X server so that the X server ca

Overall this isn't wrong, but just to make a few corrections here... >its default is to send all your OpenGL operations to the X server so that the X server can do the actual OpenGL things This isn't the case with any modern GLX applications and also hasn't been the default on the Xorg server in many years: https://gitlab.freedesktop.org/xorg/xserver/-/commit/d0da0e9c3bb8fe0cd4879ecb24d21715bfaa209b https://gitlab.freedesktop.org/xorg/xserver/-/commit/d0da0e9... >On Unix, EGL is implemented in Mesa Confusingly, GLX is also currently implemented in Mesa. >I suspect that EGL on X is not in any way network transparent It's not, but modern GLX is not "network transparent" either. The only way you get indirect rendering with GLX is with extremely old applications (OpenGL 1.4 and earlier) and if you explicitly configure the server to use it with a flag. >I don't know how an application using EGL and OpenGL on top of a Zink backed would interact with a Vulkan WSI, but I assume that Zink plumbs it all through somehow. Zink is a Gallium driver so the WSI doesn't get used. You just use EGL and then Zink passes the Vulkan buffer back to it.