Xref: utzoo comp.unix.i386:1838 comp.windows.x:16000
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.unix.i386,comp.windows.x
Subject: Re: Shrink Wrapping X Windows Clients on Intel Hardware
Message-ID: <2734@auspex.UUCP>
Date: 18 Dec 89 22:03:22 GMT
References: <1989Dec8.005923.23810@pcrat.uucp> <129232@sun.Eng.Sun.COM>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Followup-To: comp.unix.i386
Organization: Auspex Systems, Santa Clara
Lines: 11

>Vr4 won't necessarily solve the problem of systems using
>different local connection methods;

The Transport Independent RPC white paper from Sun makes reference to a
"loopback" transport; if this is present on all flavors of S5R4, it
could potentially be used for this (I suspect it's sort of a TLI moral
equivalent to UNIX-domain sockets).

If somebody decides to use some other transport, e.g. shared memory,
that can still work, though, if (as you imply) they made "libX11"
dynamic.