Forget the windows architecture鈥攊t will confuse you on X Windows.
X Windows was designed for a client/server architecture. The server and client may be on the same machine, which is more typical now than it used to be when first developed in the 1980s.
Many people feel a certain "backwardness" of client and server in comparison to a web server or file server. The "window server" offers window services, so it is the graphic display/mouse/keyboard part of the protocol. The client is a program process.
The client connects to a server, and creates windows, adds widgets to them and then enters a loop to service events. That seems a lot like MS and Mac Windows. The difference is that events and draw commands are communicated over a TCP/IP link.
The X client program makes calls very similar to what you are used to in other window systems, but they are translated (by the X library) into bytes buffered for transmission.
The window manager is another client program and can be run from any computer which can connect to the server.
The server translates commands like "write text 'abc' " and "draw circle" into pixels onscreen. It also handles mouse and keyboard operations and notifies the connections that have registered various operation type notifications.How does the x window server system work?
An X server is an application that interacts with an application (the X client). The X server app gets it controls from the user through the keyboard and mouse and directs the application to resize, repaint, minimize, and restore its window as well and supplies to the app the characters typed in in fields the application has set up..
No comments:
Post a Comment