Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re:  X terminal question
Message-ID: <9004080538.AA02237@Larry.McRCIM.McGill.EDU>
Date: 8 Apr 90 05:38:12 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 39

> I am trying to do some work on X terminals.  I have some questions
> reagrarding the CPU that get used in a X terminal application.

> I believe that in a typical X terminal application the server
> executes on the terminal and the clients on the host.

Yes.  There are some minor exceptions, like GraphOn, which runs part of
the server on the host, and someone's X terminal which has some of the
most common clients built-in, but in general this is true.

> The CPU which is on the terminal is basically doing two jobs: 1)
> communicating over network and displaying data on the CRT.

Well, an X server is more than just an interface between the network
and the screen.  It also has to handle off-screen storage (pixmaps,
primarily) and keyboard/pointer input....

> Now I have following questions regarding X terminals.

> 1) How of the code that is running on the terminal is TCP/IP server
>    code ?

(Assuming you mean "How *much* of the...")

Never having seen source to an X terminal, I have to guess.  But I have
seen code for an X server (the MIT one) and to TCP implementations (the
Van Jacobson code, for example).  Comparing the handiest examples of X
servers and TCP code produces a count of 7962 lines for TCP/IP and
101024 lines for the X server.

> 2) [...]
> 3) [...]

I have not even a guess for those.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu