Difference between revisions of "XCB"
Chipster19 (talk | contribs) (New page: == Introduction to XCB == The XCB library provides an interface to the X Window System protocol, designed to replace the Xlib interface. It has several advantages over Xlib, including siz...) |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Package-Introduction|The XCB library provides an interface to the X Window System protocol, designed to replace the Xlib interface. It has several advantages over Xlib, including size (small library and lower memory footprint), latency hiding (batch several requests and wait for the replies later), direct protocol access (one-to-one mapping between interface and protocol), thread support (access XCB from multiple threads, with no explicit locking), and easy creation of new extensions (automatically generates its interface from machine-parsable XML protocol descriptions). Xlib can also use XCB as a transport layer, allowing software to make requests and receive responses with both, which eases porting to XCB. However, client programs, libraries, and toolkits will gain the most benefit from a native XCB port.|http://xcb.freedesktop.org/}} | |
| − | |||
| − | The XCB library provides an interface to the X Window System protocol, designed to replace the Xlib interface. It has several advantages over Xlib, including size (small library and lower memory footprint), latency hiding (batch several requests and wait for the replies later), direct protocol access (one-to-one mapping between interface and protocol), thread support (access XCB from multiple threads, with no explicit locking), and easy creation of new extensions (automatically generates its interface from machine-parsable XML protocol descriptions). Xlib can also use XCB as a transport layer, allowing software to make requests and receive responses with both, which eases porting to XCB. However, client programs, libraries, and toolkits will gain the most benefit from a native XCB port. | ||
| − | |||
| − | |||
== Sections of XCB == | == Sections of XCB == | ||
* [[xcb-proto]] | * [[xcb-proto]] | ||
| − | |||
* [[libxcb]] | * [[libxcb]] | ||
* [[xcb-utils]] | * [[xcb-utils]] | ||
| − | + | ||
| − | + | [[Category:X Libs]] | |
Latest revision as of 19:40, 5 December 2010
Introduction to XCB
The XCB library provides an interface to the X Window System protocol, designed to replace the Xlib interface. It has several advantages over Xlib, including size (small library and lower memory footprint), latency hiding (batch several requests and wait for the replies later), direct protocol access (one-to-one mapping between interface and protocol), thread support (access XCB from multiple threads, with no explicit locking), and easy creation of new extensions (automatically generates its interface from machine-parsable XML protocol descriptions). Xlib can also use XCB as a transport layer, allowing software to make requests and receive responses with both, which eases porting to XCB. However, client programs, libraries, and toolkits will gain the most benefit from a native XCB port.
Project Homepage: http://xcb.freedesktop.org/
