Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!unido!laura!tommy!klute
From: klute@tommy.informatik.uni-dortmund.de (Rainer Klute)
Newsgroups: comp.windows.x
Subject: Re: Robust multi-display clients
Message-ID: <3239@laura.UUCP>
Date: 8 May 91 15:20:57 GMT
References: <WALT.91May4173316@arrisun3.utarl.edu>
Sender: news@laura.UUCP
Distribution: comp
Organization: University of Dortmund, Germany
Lines: 20

In article <WALT.91May4173316@arrisun3.utarl.edu>,
Buehring@Intellection.COM (Walt Buehring) writes:
|> 2. Split UI and application into separate processes and fork a UI
|> process for each display.  Communicate with application code thru IPC
|> channel via some home-grown command protocol.
|> 
|> Disadvantage:
|>         - You may end up context switching your guts out.
|>         - Given the size of Xt and Motif libraries, each UI process
|>           may become *huge* and impose severe paging penalties.
|>         - Access to application code and data is made cumbersome.

Another disadvantage: The application won't run under operating systems
without fork().

-- 
  Dipl.-Inform. Rainer Klute      klute@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB             klute@unido.uucp, klute@unido.bitnet
  Postfach 500500         |)|/    Tel.: +49 231 755-4663
D-4600 Dortmund 50        |\|\    Fax : +49 231 755-2386