Hacker News Reader

Comment by ihsw | Hacker News Reader

> No, that is outside the scope of Wayland. To support remote rendering you need to define a rendering API, which is something I've been very careful to avoid doing. The reason Wayland is so simple and feasible at all is that I'm sidestepping this big task and pushing it to the clients. It's an interesting challenge, a very big task and it's hard to get right, but essentially orthogonal to what Wayland tries to achieve.

Source: http://wayland.freedesktop.org/faq.html#heading_toc_j_8

View on HN

To support remote rendering you need to define a rendering API

See, this makes no sense to me. The truth of this statement holds if I substitute s/remote/local/.

The fact is, Wayland manages a shared resource via a well-known API. This is the very definition of client/server architecture. There's no additional technical hurdle to be crossed to support network transparency.

Yes, but the resources it passes around are handles to buffers in memory (as little copying as possible). Not so trivial to pass around the network (well, most networks). I suspect a VNC-like approach would work easiest and most generally, but performance would suffer (though I've found situations where VNC beats remote X11, even over very low latency connections).

My understanding of OpenGL (which could be wrong) is that buffers are only transferred when loading textures onto the graphics card, which generally only happens at startup, and is time-consuming anyway (since they must find their way from disk to graphics memory).

So memory buffer handles can still be passed around, since clients rarely touch the raw data. (Indeed, this is exactly how X11 works.)

You can send OpenGL over the network, but I suspect sending the rendered window contents will use less bandwidth. So that's what Wayland is going to do.

Modern X applications mostly shuffle around pixmaps anyway. X11 drawing primitives are not used very often at all.

Reply on news.ycombinator.com