Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!stanford.edu!snorkelwacker.mit.edu!bloom-beacon!dont-send-mail-to-path-lines
From: mouse@lightning.mcrcim.mcgill.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: Robust multi-display clients
Message-ID: <9105082345.AA01947@lightning.McRCIM.McGill.EDU>
Date: 8 May 91 23:45:33 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 19

>> 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.

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

Under "advantages", the poster listed the possibility of having the
application code and the UI code on separate machines.  This brings up
the possibility of splitting the application into two: an "application
server" and a "user interface".  The UI program can then be considered
a client of both the X server and the application server.

If you do this, you no longer need to depend on fork()....

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu