a86fd86b5e
The patch adds a listener called after an event has been dispatched by the server. Wayland servers that incorporate the Wayland display into their own event loops may dispatch multiple Wayland events to clients as they work through their task queues. For e.g. if system display state changes the Wayland server may emit several output / surface Wayland events to connected clients. Currently an explicit flush is performd immediately after each individual Wayland event is dispatched to make sure these are propagated to clients in a deterministic / reliable manner. This results in hard to maintain / easy to break code. Contributors must make sure to explicitly flush when dispatching Wayland events to clients - or otherwise wait for some other server event to flush the client buffer later on. In the latter case behavior is not deterministic and makes testing the server code much harder. The client event_dispatch_listener added in this patch allows the server to track if the processing of a server event has resulted in the dispatch of one or more Wayland events to clients - and ensure the buffer is appropriately flushed. This eliminates the need to flush in many different areas of the codebase, making the server easier to maintain and test. Signed-off-by: Thomas Lukaszewicz <thomaslukaszewicz@gmail.com> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| cursor | ||
| doc | ||
| egl | ||
| protocol | ||
| src | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .triage-policies.yml | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| meson.build | ||
| meson_options.txt | ||
| README.md | ||
| release.sh | ||
| releasing.txt | ||
| wayland-scanner.m4 | ||
| wayland-scanner.mk | ||
Wayland
Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.
The wayland protocol is essentially only about input handling and buffer management. The compositor receives input events and forwards them to the relevant client. The clients creates buffers and renders into them and notifies the compositor when it needs to redraw. The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor. However, the protocol does not handle rendering, which is one of the features that makes wayland so simple. All clients are expected to handle rendering themselves, typically through cairo or OpenGL.
Building the wayland libraries is fairly simple, aside from libffi, they don't have many dependencies:
$ git clone https://gitlab.freedesktop.org/wayland/wayland
$ cd wayland
$ meson build/ --prefix=PREFIX
$ ninja -C build/ install
where PREFIX is where you want to install the libraries.
See https://wayland.freedesktop.org for documentation.