Binaries compiled for one platform but executed on another may not interpret a
blank hostname field in the displayspec correctly. For example, binaries compiled for
SCO Unix may default to a Streams mechanism. When running under Linux using
the iBCS compatibility layer, this will cause a problem, because Linux doesn??™t support
Streams. In this case, a hostname value of unix should force the use of Unix
domain sockets; as a last resort, the TCP/IP local loopback mechanism can be used
by specifying a hostname of localhost (however, this incurs the extra overhead of the
TCP/IP stack??”twice).
1.15 Server Extensions
The X11 protocol was designed to be enhanced by adding extensions to the X server.
Clients can query the server to find out what extensions are available. This has
enabled many features to be added through the years without significant changes to
the core protocol (which explains why we??™re still using version 11!).
Extensions may be compiled in to the X server, or they may be loaded as modules.
Because their presence is optional, the X server can be slimmed down for use on
small machines by building it with a smaller set of extensions.
Here are some of the key extensions in widespread use (upper- and lowercase names
are those reported by the extensions themselves using xdpyinfo (Section 6.
Pages:
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61