dmx/doc/DMXSpec-v1.txt

39     about the characteristics of the Xdmx server and the back-end X
87     This request returns the number of back-end screens that the Xdmx
88     server controls.  A back-end screen may be managed as a regular X
89     screen in the Xdmx server or may be joined with other back-end
110     This request returns information about individual back-end screens.
117     back-end screen.  This request will always return non-negative
146     about how the window is represented on the back-end X servers.  For
147     each back-end X server that displays a portion of the window, the
152         2) the window ID on the back-end X server of the window
154         3) the position and dimensions of the window on the back-end, in
156         4) the visible area of the window on the back-end, in
159     Note that DMX allows multiple back-end windows to overlap in their
161     have to be completely covered by back-end windows -- there may be
165     1024x768 back-end displays (A and B) of a 2048x1536 DMX display
166     composed of 4 1024x768 back-end displays arranged in a cube:
173     display A: 500x500 window at 1024-250,0 (relative to back end)
176     display B: 500x500 window at -250,0 (relative to back end)
185     might be buffered in xlib while requests directly to the back-end X
187     DMXSync before talking directly to the back-end X servers.
227         2 for back-end devices.
236     For back-end devices, the physicalScreen will identify the back-end
239     on the back-end X server; and the name will be invalid (since it
261     created on the back-end X servers until they are required.  This
290     server and each back-end X server.  It is used by a client that
291     talks directly to back-end X servers