49 on the system. Each client thread opens a session to the server, and issues |
49 on the system. Each client thread opens a session to the server, and issues |
50 requests for service. </p> <fig id="GUID-4EEE0DBF-A4DC-59A1-8310-504BF05204C7"> |
50 requests for service. </p> <fig id="GUID-4EEE0DBF-A4DC-59A1-8310-504BF05204C7"> |
51 <title> Window Server </title> |
51 <title> Window Server </title> |
52 <desc><p>The Window Server controls access by many client applications, to |
52 <desc><p>The Window Server controls access by many client applications, to |
53 the machine’s screen, keyboard and pointer. </p> </desc> |
53 the machine’s screen, keyboard and pointer. </p> </desc> |
54 <image href="GUID-FE4BBEB4-4E5A-5BF2-A72F-AF53BAD83518_d0e210339_href.png" placement="inline"/> |
54 <image href="GUID-FE4BBEB4-4E5A-5BF2-A72F-AF53BAD83518_d0e237850_href.png" placement="inline"/> |
55 </fig> <p>The Window Server thread runs at a higher priority than any application; |
55 </fig> <p>The Window Server thread runs at a higher priority than any application; |
56 only the kernel runs at a higher priority. Therefore, all applications' requests |
56 only the kernel runs at a higher priority. Therefore, all applications' requests |
57 for screen updates, and all handling of machine events such as pointers and |
57 for screen updates, and all handling of machine events such as pointers and |
58 keys, are handled at higher priority than any individual application. </p> <p>Each |
58 keys, are handled at higher priority than any individual application. </p> <p>Each |
59 client application runs in its own thread. The Window Server presents an interface |
59 client application runs in its own thread. The Window Server presents an interface |
71 and draw to them. </p> </section> |
71 and draw to them. </p> </section> |
72 <section id="GUID-A8BCF1C1-A637-4DDC-9249-BCEF4E23BA06"><title>Window server client-side API</title> <p>The following diagram |
72 <section id="GUID-A8BCF1C1-A637-4DDC-9249-BCEF4E23BA06"><title>Window server client-side API</title> <p>The following diagram |
73 shows the key classes in the Window Server client-side library. Below the |
73 shows the key classes in the Window Server client-side library. Below the |
74 diagram we provide a summary of the key concepts. </p> <fig id="GUID-A84A2706-1AF0-598B-976E-0980AD69E6E7"> |
74 diagram we provide a summary of the key concepts. </p> <fig id="GUID-A84A2706-1AF0-598B-976E-0980AD69E6E7"> |
75 <title> Window Server client-side API classes </title> |
75 <title> Window Server client-side API classes </title> |
76 <image href="GUID-FEFF353E-DE8A-5FBA-B696-CD01D06BE813_d0e210364_href.png" placement="inline"/> |
76 <image href="GUID-FEFF353E-DE8A-5FBA-B696-CD01D06BE813_d0e237875_href.png" placement="inline"/> |
77 </fig> <table id="GUID-37EDAB58-6F7B-526A-8E46-891598924120"> |
77 </fig> <table id="GUID-37EDAB58-6F7B-526A-8E46-891598924120"> |
78 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
78 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
79 <thead> |
79 <thead> |
80 <row> |
80 <row> |
81 <entry>Concept</entry> |
81 <entry>Concept</entry> |