Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!wugate!uunet!mcsun!ukc!kl-cs!nott-cs!ucl-cs!J.Crowcroft
From: J.Crowcroft@ucl-cs.UUCP
Newsgroups: comp.windows.x
Subject: X over ISO transport
Message-ID: <470@ucl-cs.UUCP>
Date: 14 Nov 89 16:33:24 GMT
Sender: J.Crowcroft@ucl-cs.UUCP
Lines: 30

From: Jon Crowcroft <J.Crowcroft@uk.ac.ucl.cs>


Using the ISODE Transport Service code, i have succesfully built an
X server and a few clients! 

These a strictly experimental (like an existence proof) and not very
heavily tested at all, but a couple of interesting things came to
light in the process:

1. putting transport in does not appear to impair the performance
noticably.

2. It does increase the process size by O(100k) per process, so if
you're short on memory, you might want a smaller transport (or else
wait til it appears in U**x kernels...).

3. The X interface to TCP/DECNET was clearly well written, since it
fell out quite nicely onto ISODE transport service interface.

4. Security and Nameing in X need some overhaul - the :/::
distinguishing of TCP/DECNET is unsatisfactory...the per host access
control is too simple. the XHost structure aint big enough for ISO
addresseses!!

any questions?

cheers

jon