1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
5 <!--translated from sync.tex, on 2010-06-29 10:52:00,
6 by TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/) xhtml,docbook,html,refcaption -->
12 <title>X Synchronization Extention Protocol</title>
13 <subtitle>X Consortium Standard</subtitle>
14 <releaseinfo>X Version 11, Release 6.6.84</releaseinfo>
17 <firstname>Tim</firstname><surname>Glauert</surname>
18 <affiliation><orgname>Olivetti Research/MultiWorks</orgname></affiliation>
21 <firstname>Dave</firstname>
22 <surname>Carver</surname>
23 <affiliation><orgname>Digital EquipmentCorporation, MIT/Project Athena</orgname></affiliation>
26 <firstname>Jim</firstname>
27 <surname>Gettys</surname>
28 <affiliation><orgname>Digital EquipmentCorporation, Cambridge Research Laboratory</orgname></affiliation>
31 <firstname>David</firstname>
32 <surname>Wiggins</surname>
33 <affiliation><orgname>X Consortium, Inc.</orgname></affiliation>
36 <corpname>X Consortium Standard</corpname>
41 Olivetti Research Limited, Cambridge England and
42 Digital Equipment Corporation, Maynard, Massachusetts
45 <copyright><year>1991</year><holder>X Consortium</holder></copyright>
47 <releaseinfo>Version 3.0</releaseinfo>
48 <affiliation><orgname>X Consortium</orgname></affiliation>
49 <productnumber>X Version 11, Release 6.8</productnumber>
53 Permission to use, copy, modify, and distribute this documentation for any
54 purpose and without fee is hereby granted, provided that the above
55 copyright notice appear in all copies. Olivetti, Digital, MIT, and the
56 X Consortium make no representations about the suitability for any purpose
57 of the information in this document. This documentation is provided as
58 is without express or implied warranty.
62 Permission is hereby granted, free of charge, to any person obtaining
63 a copy of this software and associated documentation files
64 (the "Software"), to deal in the Software without
65 restriction, including without limitation the rights to use, copy,
66 modify, merge, publish, distribute, sublicense, and/or sell copies of
67 the Software, and to permit persons to whom the Software is furnished
68 to do so, subject to the following conditions:
71 <para>The above copyright notice and this permission notice shall be included
72 in all copies or substantial portions of the Software.</para>
74 <para>THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY
75 KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
76 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO
77 EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
78 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
79 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
82 <para>Except as contained in this notice, the name of the X Consortium shall
83 not be used in advertising or otherwise to promote the sale, use or other
84 dealings in this Software without prior written authorization from the X
90 <chapter id="synchronization_protocol">
91 <title>Synchronization Protocol</title>
93 The core X protocol makes no guarantees about the relative order of execution
94 of requests for different clients. This means that any synchronization between
95 clients must be done at the client level in an operating system-dependent and
96 network-dependent manner. Even if there was an accepted standard for such
97 synchronization, the use of a network introduces unpredictable delays between
98 the synchronization of the clients and the delivery of the resulting requests
103 The core X protocol also makes no guarantees about the time at which requests
104 are executed, which means that all clients with real-time constraints must
105 implement their timing on the host computer. Any such timings are subject to
106 error introduced by delays within the operating system and network and are
107 inefficient because of the need for round-trip requests that keep the client
108 and server synchronized.
112 The synchronization extension provides primitives that allow synchronization
113 between clients to take place entirely within the X server. This removes any
114 error introduced by the network and makes it possible to synchronize clients
115 on different hosts running different operating systems. This is important for
116 multimedia applications, where audio, video, and graphics data streams are
117 being synchronized. The extension also provides internal timers within the
118 X server to which client requests can be synchronized. This allows simple
119 animation applications to be implemented without any round-trip requests and
120 makes best use of buffering within the client, network, and server.
123 <sect1 id="description">
124 <title>Description</title>
126 The mechanism used by this extension for synchronization within the X
127 server is to block the processing of requests from a client until a
128 specific synchronization condition occurs. When the condition occurs, the
129 client is released and processing of requests continues. Multiple clients
130 may block on the same condition to give inter-client synchronization.
131 Alternatively, a single client may block on a condition such as an animation
136 The extension adds <function>Counter</function> and
137 <function>Alarm</function> to the set of resources managed by the
138 server. A counter has a 64-bit integer value that may be increased or
139 decreased by client requests or by the server internally. A client can block
140 by sending an Await request that waits until one of a set of synchronization
141 conditions, called TRIGGERs, becomes TRUE.
145 The <function>CreateCounter</function> request allows a client to create a
146 <function>Counter</function> that can be changed by explicit
147 <function>SetCounter</function> and <function>ChangeCounter</function>
148 requests. These can be used to implement synchronization between different
153 There are some counters, called <function>System Counters</function>, that
154 are changed by the server internally rather than by client requests. The
155 effect of any change to a system counter is not visible until the server
156 has finished processing the current request. In other words, system
157 counters are apparently updated in the gaps between the execution of
158 requests rather than during the actual execution of a request. The extension
159 provides a system counter that advances with the server time as defined by
160 the core protocol, and it may also provide counters that advance with the
161 real-world time or that change each time the CRT screen is refreshed.
162 Other extensions may provide their own extension-specific system counters.
166 The extension provides an <function>Alarm</function> mechanism that allows
167 clients to receive an event on a regular basis when a particular counter
175 Please refer to the X11 Protocol specification as this document uses
176 syntactic conventions established there and references types defined there.
179 <para>The following new types are used by the extension.</para>
181 <literallayout class="monospaced">
182 INT64: 64-bit signed integer
184 VALUETYPE: {Absolute,Relative};
185 TESTTYPE: {PositiveTransition,NegativeTransition,
186 PositiveComparison,NegativeComparison}
189 value-type:VALUETYPE,
195 event-threshold:INT64
203 ALARMSTATE: {Active,Inactive,Destroyed}
207 The COUNTER type defines the client-side handle on a server
208 <function>Counter</function>. The value of a counter is an INT64.
212 The TRIGGER type defines a test on a counter that is either TRUE or FALSE. The
213 value of the test is determined by the combination of a test value, the value
214 of the counter, and the specified test-type.
218 The test value for a trigger is calculated using the value-type and
219 wait-value fields when the trigger is initialized. If the value-type field
220 is not one of the named VALUETYPE constants, the request that initialized the
221 trigger will return a <function>Value</function> error. If the value-type
222 field is <function>Absolute</function>, the test value is given by the
223 wait-value field. If the value-type field is <function>Relative</function>,
224 the test value is obtained by adding the wait-value field to the value of the
225 counter. If the resulting test value would lie outside the range for an
226 INT64, the request that initialized the trigger will return a
227 <function>Value</function> error. If counter is <function>None</function>
228 and the value-type is <function>Relative</function>, the request that
229 initialized the trigger will return a <function>Match</function> error. If
230 counter is not None and does not name a valid counter, a Counter error is
235 If the test-type is <function>PositiveTransition</function>, the trigger is
236 initialized to FALSE, and it will become TRUE when the counter changes from
237 a value less than the test value to a value greater than or equal to the
238 test value. If the test-type is <function>NegativeTransition</function>,
239 the trigger is initialize to FALSE, and it will become TRUE when the counter
240 changes from a value greater than the test value to a value less than or
241 equal to the test value. If the test-type is
242 <function>PositiveComparison</function>, the trigger is TRUE if the
243 counter is greater than or equal to the test value and FALSE otherwise. If the
244 test-type is <function>NegativeComparison</function>, the trigger is TRUE
245 if the counter is less than or equal to the test value and FALSE otherwise.
246 If the test-type is not one of the named TESTTYPE constants, the request that
247 initialized the trigger will return a Value error. A trigger with a counter
248 value of <function>None</function> and a valid test-type is always TRUE.
252 The WAITCONDITION type is simply a trigger with an associated event-threshold.
253 The event threshold is used by the <function>Await</function> request to
254 decide whether or not to generate an event to the client after the trigger has
255 become TRUE. By setting the event-threshold to an appropriate value, it is
256 possible to detect the situation where an <function>Await</function> request
257 was processed after the TRIGGER became TRUE, which usually indicates that
258 the server is not processing requests as fast as the client expects.
262 The SYSTEMCOUNTER type provides the client with information about a
263 <function>System</function>Counter. The name field is the textual name of
264 the counter that identifies the counter to the client. The counter field
265 is the client-side handle that should be used in requests that require a
266 counter. The resolution field gives the approximate step size of the system
267 counter. This is a hint to the client
268 that the extension may not be able to resolve two wait conditions with test
269 values that differ by less than this step size. A microsecond clock, for
270 example, may advance in steps of 64 microseconds, so a counter based on this
271 clock would have a resolution of 64.
275 The only system counter that is guaranteed to be present is called SERVERTIME,
276 which counts milliseconds from some arbitrary starting point. The least
277 significant 32 bits of this counter track the value of Time used by the
278 server in Events and Requests. Other system counters may be provided by
279 different implementations of the extension. The X Consortium will maintain a
280 registry of system counter names to avoid collisions in the name space.
284 An ALARM is the client-side handle on an <function>Alarm</function> resource.
289 <title>Errors</title>
296 This error is generated if the value for a COUNTER argument in a request
297 does not name a defined COUNTER.
305 This error is generated if the value for an ALARM argument in a request
306 does not name a defined ALARM.
313 <sect1 id="requests">
315 <title>Requests</title>
319 <term>Initialize</term>
321 <literallayout class="monospaced">
322 version-major,version-minor: CARD8
324 version-major,version-minor: CARD8
328 This request must be executed before any other requests for this extension. If a
329 client violates this rule, the results of all SYNC requests that it issues are
330 undefined. The request takes the version number of the extension that the
331 client wishes to use and returns the actual version number being implemented
332 by the extension for this client. The extension may return different
333 version numbers to a client depending of the version number supplied by
334 that client. This request should be executed only once for each client
338 Given two different versions of the SYNC protocol, v1 and v2, v1 is
339 compatible with v2 if and only if v1.version_major = v2.version_major
340 and v1.version_minor <= v2.version_minor. Compatible means that the
341 functionality is fully supported in an identical fashion in the two versions.
344 This document describes major version 3, minor version 0 of the SYNC protocol.
349 <term>ListSystemCounters</term>
351 <literallayout class="monospaced">
353 system-counters: LISTofSYSTEMCOUNTER
357 This request returns a list of all the system counters that are available at
358 the time the request is executed, which includes the system counters
359 that are maintained by other extensions. The list returned by this
360 request may change as counters are created and destroyed by other extensions.
365 <term>CreateCounter</term>
367 <literallayout class="monospaced">
370 Errors: IDChoice,Alloc
373 This request creates a counter and assigns the specified id to it. The counter
374 value is initialized to the specified initial-value and there are no clients
375 waiting on the counter.
380 <term>DestroyCounter</term>
382 <literallayout class="monospaced">
384 Errors: Counter,Access
387 This request destroys the given counter and sets the counter fields for all
388 triggers that specify this counter to <function>None</function>. All clients
389 waiting on the counter are released and a <function>CounterNotify</function>
390 event with the destroyed field set to TRUE is sent to each waiting client,
391 regardless of the event-threshold. All alarms specifying the counter become
392 <function>Inactive</function> and an <function>AlarmNotify</function>
393 event with a state field of <function>Inactive</function> is generated. A
394 counter is destroyed automatically when the connection to the creating client
395 is closed down if the close-down mode is Destroy. An
396 <function>Access</function> error is generated if counter is a system
397 counter. A <function>Counter</function> error is generated if counter does
398 not name a valid counter.
403 <term>QueryCounter</term>
405 <literallayout class="monospaced">
409 Errors: <function>Counter</function>
412 This request returns the current value of the given counter or a generates
413 Counter error if counter does not name a valid counter.
420 <literallayout class="monospaced">
421 wait-list: LISTofWAITCONDITION
422 Errors: Counter,Alloc,Value
425 When this request is executed, the triggers in the wait-list are initialized
426 using the wait-value and value-type fields, as described in the definition of
427 TRIGGER above. The processing of further requests for the client is blocked
428 until one or more of the triggers becomes TRUE. This may happen immediately,
429 as a result of the initialization, or at some later time, as a result of
430 a subsequent <function>SetCounter</function>,
431 <function>ChangeCounter</function> or
432 <function>DestroyCounter</function> request.
435 A Value error is generated if wait-list is empty.
438 When the client becomes unblocked, each trigger is checked to determine
439 whether a <function>CounterNotify</function> event should be generated.
440 The difference between the counter and the test value is calculated by
441 subtracting the test value from the value of the counter. If the test-type
442 is <function>PositiveTransition</function> or
443 <function>PositiveComparison</function>, a
444 <function>CounterNotify</function> event is generated if the difference is
445 at least event-threshold. If the test-type is
446 <function>NegativeTransition</function> or
447 <function>NegativeComparison</function>, a
448 <function>CounterNotify</function> event is generated if the difference
449 is at most event-threshold. If the difference lies outside the range for an
450 INT64, an event is not generated.
453 This threshold check is made for each trigger in the list and a
454 <function>CounterNotify</function> event is generated for every trigger for
455 which the check succeeds. The check for
456 <function>CounterNotify</function> events is performed even if one of the
457 triggers is TRUE when the request is first executed. Note that a
458 <function>CounterNotify</function> event may be generated for a trigger
459 that is FALSE if there are multiple triggers in the request. A
460 <function>CounterNotify</function> event with the destroyed flag set to
461 TRUE is always generated if the counter for one of the triggers is
467 <term>ChangeCounter</term>
469 <literallayout class="monospaced">
472 Errors: <function>Counter,Access,Value</function>
475 This request changes the given counter by adding amount to the current
476 counter value. If the change to this counter satisfies a trigger for which a client
477 is waiting, that client is unblocked and one or more
478 <function>CounterNotify</function> events may be generated. If the change to
479 the counter satisfies the trigger for an alarm, an
480 <function>AlarmNotify</function> event is generated and the
481 alarm is updated. An <function>Access</function> error is generated if
482 counter is a system counter. A <function>Counter</function> error is
483 generated if counter does not name a valid counter. If the resulting value
484 for the counter would be outside the range for an INT64, a
485 <function>Value</function> error is generated and the counter is not changed.
488 It should be noted that all the clients whose triggers are satisfied by this
489 change are unblocked, so this request cannot be used to implement mutual
495 <term>SetCounter</term>
497 <literallayout class="monospaced">
500 Errors: <function>Counter,Access</function>
503 This request sets the value of the given counter to value. The effect is
504 equivalent to executing the appropriate ChangeCounter request to change
505 the counter value to value. An Access error is generated if counter names a
506 system counter. A Counter error is generated if counter does not name a valid
512 <term>CreateAlarm</term>
514 <literallayout class="monospaced">
517 values-list: LISTofVALUE
518 left">Errors: IDChoice,Counter,Match,Value,Alloc
521 This request creates an alarm and assigns the identifier id to it. The
522 values-mask and values-list specify the attributes that are to be explicitly
523 initialized. The attributes for an Alarm and their defaults are:
527 <colspec colname="c1"/>
528 <colspec colname="c2"/>
529 <colspec colname="c3"/>
530 <colspec colname="c4"/>
533 <entry align="left">Attribute</entry>
534 <entry align="left">Type</entry>
535 <entry align="left">Default</entry>
538 <entry rowsep="1"></entry>
539 <entry rowsep="1"></entry>
540 <entry rowsep="1"></entry>
541 <entry rowsep="1"></entry>
544 <entry align="left">trigger</entry>
545 <entry align="left">TRIGGER</entry>
546 <entry align="left">counter</entry>
547 <entry align="left">None</entry>
550 <entry align="left"></entry>
551 <entry align="left"></entry>
552 <entry align="left">value-type</entry>
553 <entry align="left">Absolute</entry>
556 <entry align="left"></entry>
557 <entry align="left"></entry>
558 <entry align="left">value</entry>
559 <entry align="left">0</entry>
562 <entry align="left"></entry>
563 <entry align="left"></entry>
564 <entry align="left">test-type</entry>
565 <entry align="left">PositiveComparison</entry>
568 <entry align="left">delta</entry>
569 <entry align="left">INT64</entry>
570 <entry align="left">1</entry>
573 <entry align="left">events</entry>
574 <entry align="left">BOOL</entry>
575 <entry align="left">TRUE</entry>
581 The trigger is initialized as described in the definition of TRIGGER, with an
582 error being generated if necessary.
585 If the counter is <function>None</function>, the state of the alarm is set
586 to <function>Inactive</function>, else it is set to Active.
589 Whenever the trigger becomes TRUE, either as a result of this request or as the
590 result of a <function>SetCounter</function>,
591 <function>ChangeCounter</function>, <function>DestroyCounter</function>, or
592 <function>ChangeAlarm</function> request, an
593 <function>AlarmNotify</function> event is generated and the alarm is
594 updated. The alarm is updated by repeatedly adding delta to the value of the
595 trigger and reinitializing it until it becomes FALSE. If this update would
596 cause value to fall outside the range for an INT64, or if the counter
597 value is <function>None</function>, or if the delta is 0 and test-type
598 is <function>PositiveComparison</function> or
599 <function>NegativeComparison</function>, no change is made to value and
600 the alarm state is changed to <function>Inactive</function> before the
601 event is generated. No further events are generated by an
602 <function>Inactive</function> alarm until a <function>ChangeAlarm</function>
603 or <function>DestroyAlarm </function> request is executed.
606 If the test-type is <function>PositiveComparison</function> or
607 <function>PositiveTransition and</function> delta is less than zero, or
608 if the test-type is <function>NegativeComparison</function> or
609 <function>NegativeTransition</function> and delta is greater than zero,
610 a <function>Match</function> error is generated.
613 The events value enables or disables delivery of
614 <function>AlarmNotify</function> events
615 to the requesting client. The alarm keeps a separate event flag for
616 each client so that other clients may select to receive events from this
620 An <function>AlarmNotify</function> event is always generated at some time
621 after the execution of a <function>CreateAlarm</function> request. This
622 will happen immediately if the trigger is TRUE, or it will happen later
623 when the trigger becomes TRUE or the Alarm is destroyed.
628 <term>ChangeAlarm</term>
630 <literallayout class="monospaced">
633 values-list: LISTofVALUE
634 Errors: Alarm,Counter,Value,Match
637 This request changes the parameters of an Alarm. All of the parameters
638 specified for the <function>CreateAlarm</function> request may be changed
639 using this request. The trigger is reinitialized and an
640 <function>AlarmNotify</function> event is generated if appropriate, as
641 explained in the description of the <function>CreateAlarm</function> request.
644 Changes to the events flag affect the event delivery to the requesting
645 client only and may be used by a client to select or deselect event delivery
646 from an alarm created by another client.
649 The order in which attributes are verified and altered is server-dependent.
650 If an error is generated, a subset of the attributes may have been altered.
655 <term>DestroyAlarm</term>
657 <literallayout class="monospaced">
662 This request destroys an alarm. An alarm is automatically destroyed when the
663 creating client is closed down if the close-down mode is
664 <function>Destroy</function>. When an alarm is destroyed, an
665 <function>AlarmNotify</function> event is generated with a state value of
666 <function>Destroyed</function>.
671 <term>QueryAlarm</term>
673 <literallayout class="monospaced">
678 events: ALARMEVENTMASK
680 Errors: <function>Alarm</function>
682 <para>This request retrieves the current parameters for an Alarm.</para>
686 <term>SetPriority</term>
688 <literallayout class="monospaced">
691 Errors: <function>Match</function>
694 This request changes the scheduling priority of the client that created
695 client-resource. If client-resource is <function>None</function>, then
696 the priority for the client making the request is changed. A
697 <function>Match</function> error is generated if client-resource is not
698 <function>None</function> and does not name an existing resource in the
699 server. For any two priority values, A and B, A is higher priority if
700 and only if A is greater than B.
703 The priority of a client is set to 0 when the initial client connection is
707 The effect of different client priorities depends on the particular
708 implementation of the extension, and in some cases it may have no effect at
709 all. However, the intention is that higher priority clients will have
710 their requests executed before those of lower priority clients.
713 For most animation applications, it is desirable that animation clients be
714 given priority over nonrealtime clients. This improves the smoothness of the
715 animation on a loaded server. Because a server is free to implement very strict
716 priorities, processing requests for the highest priority client to the
717 exclusion of all others, it is important that a client that may potentially
718 monopolize the whole server, such as an animation that produces continuous
719 output as fast as it can with no rate control, is run at low rather than high
725 <term>GetPriority</term>
727 <literallayout class="monospaced">
731 Errors: <function>Match</function>
734 This request returns the scheduling priority of the client that created
735 client-resource. If client-resource is <function>None</function>, then the
736 priority for the client making the request is returned. A
737 <function>Match</function> error is generated if client-resource is
738 not <function>None</function> and does not name an existing resource in the
747 <title>Events</title>
751 <term>CounterNotify</term>
753 <literallayout class="monospaced">
762 <function>CounterNotify</function> events may be generated when a client
763 becomes unblocked after an <function>Await</function> request has been
764 processed. The wait-value is the value being waited for, and counter-value
765 is the actual value of the counter at the time the event was generated.
766 The destroyed flag is TRUE if this request was generated as the result of
767 the destruction of the counter and FALSE otherwise. The time is the server
768 time at which the event was generated.
771 When a client is unblocked, all the <function>CounterNotify</function>
772 events for the Await request are generated contiguously. If count is 0,
773 there are no more events to follow for this request. If count is n,
774 there are at least n more events to follow.
779 <term>AlarmNotify</term>
781 <literallayout class="monospaced">
789 An <function>AlarmNotify</function> event is generated when an alarm is
790 triggered. alarm-value is the test value of the trigger in the alarm when
791 it was triggered, counter-value is the value of the counter that triggered
792 the alarm, and time is the server time at which the event was generated.
793 The state is the new state of the alarm. If state is
794 <function>Inactive</function>, no more events will be generated by this
795 alarm until a <function>ChangeAlarm</function> request is executed, the alarm
796 is destroyed, or the counter for the alarm is destroyed.
804 <chapter id="encoding">
805 <title>Encoding</title>
807 Please refer to the X11 Protocol Encoding document as this section uses
808 syntactic conventions established there and references types defined there.
810 <para>The name of this extension is "SYNC".</para>
812 <sect1 id="encoding_new_types">
813 <title>Encoding New Types</title>
815 The following new types are used by the extension.
818 <literallayout class="monospaced">
825 INT64: 64-bit signed integer
829 2 n length of name in bytes
839 4 VALUETYPE wait-type
841 4 TESTTYPE test-type VALUETYPE:
846 8 INT64 event threshold
850 An INT64 is encoded in 8 bytes with the most significant 4 bytes
851 first followed by the least significant 4 bytes. Within these 4-byte
852 groups, the byte ordering determined during connection setup is used.
856 <sect1 id="encoding_errors">
857 <title>Encoding Errors</title>
858 <literallayout class="monospaced">
859 <function>Counter</function>
862 2 CARD16 sequence number
864 2 CARD16 minor opcode
867 <function>Alarm</function>
870 2 CARD16 sequence number
872 2 CARD16 minor opcode
879 <sect1 id="encoding_requests">
880 <title>Encoding Requests</title>
882 <literallayout class="monospaced">
883 <function>Initialize</function>
887 1 CARD8 major version
888 1 CARD8 minor version
893 2 CARD16 sequence number
895 1 CARD8 major version
896 1 CARD8 minor version
900 <function>ListSystemCounters</function>
907 2 CARD16 sequence number
911 4n list of SYSTEMCOUNTER system counters
913 <function>CreateCounter</function>
918 8 INT64 initial value
920 <function>DestroyCounter</function>
922 1 6 minor opcode<footnote><para>A previous version of this document gave an incorrect minor opcode</para></footnote>
928 2 CARD16 sequence number
930 8 INT64 counter value
935 1 7 minor opcode<footnote><para>A previous version of this document gave an incorrect minor opcode.</para></footnote>
936 2 1 + 7*n request length
937 28n LISTofWAITCONDITION wait conditions
941 1 4 minor opcode<footnote><para>A previous version of this document gave an incorrect minor opcode.</para></footnote>
948 1 3 minor opcode<footnote><para>A previous version of this document gave an incorrect minor opcode.</para></footnote>
958 4 BITMASK values mask
961 #x00000002 value-type
967 4n LISTofVALUE values
971 4 VALUETYPE value-type
982 4 BITMASK values mask
983 encodings as for <function>CreateAlarm</function>
984 4n LISTofVALUE values
985 encodings as for <function>CreateAlarm</function>
989 1 11 minor opcode<footnote><para>A previous version of this document gave an incorrect minor opcode.</para></footnote>
995 1 10 minor opcode<footnote><para>A previous version of this document gave an incorrect minor opcode.</para></footnote>
1001 2 CARD16 sequence number
1010 1 CARD8 major opcode
1017 1 CARD8 major opcode
1024 2 CARD16 sequence number
1033 <sect1 id="encoding_events">
1034 <title>Encoding Events</title>
1036 <literallayout class="monospaced">
1037 <function>CounterNotify</function>
1040 2 CARD16 sequence number
1043 8 INT64 counter value
1049 <function>AlarmNotify</function>
1052 2 CARD16 sequence number
1054 8 INT64 counter value
projects / framework / uifw / xorg / proto / x11proto-xext.git / blob