Read The X Window System paper by Scheifler and Gettys (reading #5), following the bulleted guideline below. This paper provides a good opportunity to try the approach of warming up by nibbling around the edges:

• Start by reading the abstract, introduction (section 1), and summary (section 11).
• Next, read just the section titles. Once you have a picture of where the authors are coming from, where they are going, and the route they are taking, you are in a much better position to dive into the real meat of the paper.
• Then, read sections 2 Requirements, 3 System Model, and 7 Exposures.
• The other sections (sections 4-6 and 8-10) are optional reading.

While reading the X Windows paper, keep in mind that a client requests a service and a server provides it. In terms of the display, the X server is running locally (and controlling the display hardware), and the X client may be running remotely (but wishes to display information to the user). For example, suppose that you are sitting in Cambridge and running a database application in California. From the point of receiving information, you are the client and the database program is the server. But from the point of view of display, the database program is the client, and the computer you are sitting in front of is the server. The database application wishes to draw windows, but only the X Windows server (running on your local computer) is permitted to directly manipulate your screen. Thus, the database program must issue (display) requests, which the X server satisfies.

This is a nice "systems" paper to read because it describes a real, working system and it explains the reasons choices where made from among design alternatives, even pointing out when choices where arbitrary. Furthermore, it is written for the most part in plain English with a minimum of jargon.

Next, read "Myth: X Demonstrates the Power of Client/Server Computing" (pages 127-128) in The UNIX-HATERS Handbook for a different perspective on the X Window System. Are the issues they raise a direct consequence of the design goals mentioned in the initial paper, or are they an implementation artifact? Notice that the UNIX-HATERS Handbook was written in 1994 and the X Window System of today may have resolved some of their issues.

Instead of relying on other people's written accounts, you may wish to explore X yourself by working through last year's Hands On #2 (X Windows). This is an entirely optional step.

After learning a bit about the X Window System, take the role of an outside technical consultant advising the developer of a new low power, low cost tablet PC. The tablet will have (relatively) limited processing power and heavy network usage will limit its battery life. Write a one-page memo to Katherine Wang, the project manager of the software design group, with your recommendation on whether the tablet should run the X Window System as its windowing system. Since you are a technical consultant, advance your recommendation based on the technical merits of the X Window System in this context. You only have one page, so it's best to focus on the most important points and justifications.

Remember to address the memo to the software design team. The Mayfield Handbook discusses the appropriate style for a business memo.

Use no more than one sheet of paper for your report. (Consult the 6.033 FAQ for formatting specifications.) We care more about quality and conciseness than the amount of content in your essay. You will not be able to address every issue in one page, so you will have to make your best argument and judiciously choose supporting facts for this one-pager.

Two copies of this assignment are due at the beginning of recitation on Thursday, February 22, 2007. The second copy will be forwarded to the writing program for evaluation.