Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!metro!kwanon!andy
From: andy@research.canon.oz.au (Andy Newman)
Newsgroups: comp.unix.internals
Subject: Re: X11 bashing
Message-ID: <1991Apr17.120919.7207@research.canon.oz.au>
Date: 17 Apr 91 12:09:19 GMT
Article-I.D.: research.1991Apr17.120919.7207
References: <26550@adm.brl.mil> <1991Apr16.210107.41817@eagle.wesleyan.edu> <1991Apr17.040918.12203@Think.COM> <14820@helios.TAMU.EDU>
Sender: andy@research.canon.oz.au (Andy Newman)
Reply-To: andy@research.canon.oz.au (Andy Newman)
Organization: Canon Information Systems Research Australia
Lines: 17

In article <14820@helios.TAMU.EDU> byron@archone.tamu.edu (Byron Rakitzis) writes:
>I think the successor to X will somehow allow dynamic reconfiguration
>of the server (via, say, an interpreted language) so that the network/context
>switch bottleneck can be reduced.

With the advances in dynamic linking a graphics server could also allow
compiled code to be used, dynamic protocol extensions with the speed of
compiled code. Main disadvantage compared to an interpreted language
would be the increased chances of crashing the graphics/windows server
but there could be ways around that with more sophisticated memory
management on a per process basis. Either way a dynamically re-configurable
(i.e. extensible) server makes a lot more sense than the current X11
setup (pity NeWS uses a PostScript-like language).
-- 
Andy Newman (andy@research.canon.oz.au) Canon Info. Systems Research Australia
"X: 2. An over-sized, over-featured, over-engineered window system developed
at MIT and widely used on UNIX systems." from the jargon file.