02c7e6d257
In order to allow simplifying the reply send path, collect the reply fragments into one buffer, instead of arbitrary number of WriteToClient() calls. This also makes it much easier for potentially new purely packet-based transports which (eg. binder) that would need their own stream parsing logic. This xres function is an exceptionally hard case, since payload is constructed step by step, and it's size only known when finished. The current way of the fragment handling still has lots of room for improvement (eg. using very small number of allocations), but leaving this for later exercise. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
X Server
The X server accepts requests from client applications to create windows, which are (normally rectangular) "virtual screens" that the client program can draw into.
Windows are then composed on the actual screen by the X server (or by a separate composite manager) as directed by the window manager, which usually communicates with the user via graphical controls such as buttons and draggable titlebars and borders.
For a comprehensive overview of X Server and X Window System, consult the following article: https://en.wikipedia.org/wiki/X_server
All questions regarding this software should be directed at the Xorg mailing list:
https://lists.freedesktop.org/mailman/listinfo/xorg
The primary development code repository can be found at:
https://gitlab.freedesktop.org/xorg/xserver
For patch submission instructions, see:
https://www.x.org/wiki/Development/Documentation/SubmittingPatches
As with other projects hosted on freedesktop.org, X.Org follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: