Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!turnkey!orchard.la.locus.com!fafnir.la.locus.com!carmen.la.locus.com!dlt From: dlt@locus.com (Dan Taylor) Newsgroups: comp.sys.amiga Subject: Re: Where should X concentrate its CPU cycles? Message-ID: Date: 29 Oct 90 22:14:47 GMT References: <2382@trlluna.trl.oz> <6877@sugar.hackercorp.com> <1990Oct24.221622.3575@zorch.SF-Bay.ORG> <47@oregon.oacis.org> Organization: Locus Computing Corporation, Los Angeles, California Lines: 33 jmeissen@oregon.oacis.org ( Staff OACIS) writes: >In article <1990Oct24.221622.3575@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes: >->peter@sugar.hackercorp.com (Peter da Silva) writes: >->> every program is responsible for scheduling) or X (where the >->> application is responsible for maintaining display integrity) it seems >->> to me a waste of time to duplicate functions needlessly. >But that's EXACTLY the problem with X. Instead of having the device which >actually performs the display function (the server) handle clip regions >and window refreshing, the application is responsible for these things,\ >which puts the burden back on the central system running multitudinous >X applications for users at distributed locations. PLUS it has to push >all this data back and forth over the local net, adding to the net load. >-- >John Meissen .............................. Oregon Advanced Computing Institute >jmeissen@oacis.org (Internet) | "That's the remarkable thing about life; >..!sequent!oacis!jmeissen (UUCP) | things are never so bad that they can't >jmeissen (BIX) | get worse." - Calvin & Hobbes NONSENSE!!!!! Even cheap X-Terminals have at least SOME "backing-store". This allows the server to "hide" windows and then redisplay them WITHOUT sending events to client processes. Given the Amiga's windowing power, unless the X implementations are REALLY screwed up, there should be excellent performance up to the point that CHIP memory is consumed. Even then, FAST RAM, even disk files, could be used as backing store, ELIMINATING window refresh, unless the client has changed some data. No client or network overhead. RT_M. -- * Dan Taylor * The opinions expressed are my own, and in no way * * dlt@locus.com * reflect those of Locus Computing Corporation. *