Editing Windowing system (section)

===Wayland===
{{Main|Wayland (protocol)}}

[[File:Wayland display server protocol.svg|thumb|300px|The Wayland display server protocol]]
{{stack|[[File:Wayland Logo.svg|right|60px|Wayland logo]]}}

Display servers that implement the Wayland display server protocol are called [[Wayland compositor]]s. Like any display server, a Wayland compositor is responsible for handling input and output for its clients and, in contrast to X11, the [[compositing]] as well. Examples are [[Weston (software)|Weston]], [[Mutter (software)|Mutter]], [[KWin]] or [[Enlightenment (software)|Enlightenment]].

Wayland compositors communicate with Wayland clients over the [[Wayland (protocol)|Wayland display server protocol]]. This protocol defines that clients can directly write data into the framebuffer using the [[EGL (OpenGL)|EGL]] [[rendering API]]. The display server still gets to decide which window is on top and thus visible to the user and also still is responsible for passing data regarding input devices from [[evdev]] to its clients.

Wayland is used to a certain degree in some Linux desktop distributions, such as [[Fedora (operating system)|Fedora]]. It is also well suited for mobile computing and has been adopted, for example, by the smartphone- and tablet-focused projects [[Tizen]], [[Sailfish OS]] and [[AsteroidOS]].

An implementation of Wayland is available under the [[MIT License]], the [[libwayland-client]] and libwayland-server libraries.

There is an ongoing effort to add Wayland support to [[ChromeOS]].<ref>{{cite web | url = https://chromium.googlesource.com/chromium/src/+/master/docs/ozone_overview.md | title = Ozone Overview | access-date = 2017-08-20}}</ref>