dmx/doc/DMXSpec.txt

39     about the characteristics of the Xdmx server and the back-end X
100     server and each back-end X server.  It is used by clients that
101     talk directly to back-end X servers to ensure that all pending Xdmx
102     requests have reached all back-end servers and have been processed
122     created on the back-end X servers until they are required.  This
138     area on a back-end server, there is usually a one-to-one
141     available area on a back-end server, and for more than one DMX
143     back-end server.
188     X(7x)) for the location of the DMX screen on the back-end screen.
189     The coordinant system of the back-end display is used.
195     screen window, and will occupy the same area of the back-end
219     and DMX root windows on the back-end X servers.
262     This request re-attaches the back-end physicalScreen to the Xdmx
263     server.  Only back-end screens that have been previously detached
264     with DMXRemoveScreen may be added.  The name of the back-end display
266     back-end screen that was detached.  Both the displayName and
321         * the back-end screen has already been detached.
343     about how the window is represented on the back-end X servers.  For
344     each back-end X server that displays a portion of the window, the
349         2) the window ID on the back-end X server of the window
351         3) the position and dimensions of the window on the back-end, in
353         4) the visible area of the window on the back-end, in
356     Note that DMX allows multiple back-end windows to overlap in their
358     have to be completely covered by back-end windows -- there may be
362     1024x768 back-end displays (A and B) of a 2048x1536 DMX display
363     composed of 4 1024x768 back-end displays arranged in a cube:
370     display A: 500x500 window at 1024-250,0 (relative to back end)
373     display B: 500x500 window at -250,0 (relative to back end)
382     might be buffered in xlib while requests directly to the back-end X
384     DMXSync before talking directly to the back-end X servers.
489         2 for back-end devices.
498     For back-end devices, the physicalScreen will identify the back-end
501     on the back-end X server; and the name will be invalid (since it
542         2 for back-end devices.
548     For back-end devices, InputPhysicalScreen will specify the screen