The documentation currently seems to imply that the Wayland server
informs the client about global objects when the client establishes a
connection. This is not (no longer?) the case; instead, the connection
is bootstrapped via a well-known instance of wl_display (object ID 1)
and its get_registry method.
Signed-off-by: Ondřej Hošek <ondrej.hosek@tuwien.ac.at>
This is useful for scanners that use knowledge of the object creation
hierarchy such as zig-wayland [1]. Currently zig-wayland uses a
hardcoded list of frozen interfaces.
[1]: https://codeberg.org/ifreund/zig-wayland
Signed-off-by: Isaac Freund <mail@isaacfreund.com>
