Return to BSD News archive
Xref: sserve comp.os.386bsd.apps:1003 comp.os.linux.misc:10679 Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!news.cs.su.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!newsserver.jvnc.net!news.cac.psu.edu!news.pop.psu.edu!news.pop.psu.edu!not-for-mail From: barr@pop.psu.edu (David Barr) Newsgroups: comp.os.386bsd.apps,comp.os.linux.misc Subject: Re: DOOM for X Date: 10 Mar 1994 16:49:52 -0500 Organization: Penn State Population Research Institute Lines: 18 Message-ID: <2lo4m0$sdt@bosnia.pop.psu.edu> References: <2lkpg5$8hn@Tut.MsState.Edu> <hastyCMEw58.FMr@netcom.com> <1994Mar10.123047.15912@swan.pyr> <hastyCMGpA7.Gu5@netcom.com> NNTP-Posting-Host: bosnia.pop.psu.edu In article <hastyCMGpA7.Gu5@netcom.com>, Amancio Hasty Jr <hasty@netcom.com> wrote: >Apparently yes, any client-server model which forces you to always have >two processes to communicate with each other is a broken architecture. So, tell us, how do you have a client-server model without having a client process and a server process? I agree that X the wrong platform for doing high-speed and time-critical graphics applications like video-style games. There are extensions (not SHM) that help a little, but there are lots of advantages to taking direct control of the hardware. The result is _not_ client-server. --Dave -- "Don't ever take a fence down until you know why it was put up." - Robert Frost