Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU.UUCP
Newsgroups: comp.windows.x
Subject: Re: X windows for Mac?
Message-ID: <870326141247.3.RWS@KILLINGTON.LCS.MIT.EDU>
Date: Thu, 26-Mar-87 14:12:00 EST
Article-I.D.: KILLINGT.870326141247.3.RWS
Posted: Thu Mar 26 14:12:00 1987
Date-Received: Sat, 28-Mar-87 04:55:26 EST
References: <2901@sdcsvax.UCSD.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 13


    X windows requires the ability to make a local socket connection.
    The AppleTalk design inexplicably excludes this concept.

    It also requires multi-tasking.  You can fake a background server
    with a series of clever hacks (as did Mac/IP) but this is a lot of 
    work and probably not worth the effort.

My belief is that there are people who think they know how to solve
this problem "the right way".  One easy way of solving it is to
run the "front end" of the server on some other machine, and treat
the Mac as an intelligent device, and define your own protocol
and encoding for the single serial or AppleTalk connection to it.