Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!bingvaxu!sunybcs!boulder!stan!dce From: dce@stan.UUCP (David Elliott) Newsgroups: comp.windows.x Subject: Re: A Thought on X Terminals Message-ID: <474@salgado.stan.UUCP> Date: 18 Feb 89 15:45:07 GMT References: <19613@agate.BERKELEY.EDU> <611@gt-eedsp.UUCP> <74@torsqnt.UUCP> Reply-To: dce@salgado.UUCP (David Elliott) Distribution: comp Organization: Solbourne Computer Inc., Longmont, Colorado Lines: 22 In article <74@torsqnt.UUCP> david@torsqnt.UUCP (David Haynes) writes: >In article <611@gt-eedsp.UUCP> jensen@gt-eedsp.UUCP (P. Allen Jensen) writes: >> >>Many of the X Terminal systems I have looked at (NCD in particular) can down- >>load the server from another system. This would seem to be reasonable, > >I have a problem with this. With vendors such as Oracle coming out >with X-based tools (CASE in this example) X terminals will be Isn't the word "can" the operative one here? Maybe I've been given the wrong impression, but I thought that the NCD normally kept a copy of the server in memory, and that the only reason it had download capability was so that if you needed to download a new version of the server (or even another type of graphics subsystem!), you could do so instead of having to pop the case and change the PROMs. This is similar to EEPROMs found in some other types of products. -- David Elliott ...!pyramid!boulder!stan!dce "Splish splash, I was rakin' in the cash" -- Eno