Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!i2unix!esacs!nick
From: nick@esacs.UUCP (Nikolaos Tsivranidis)
Newsgroups: comp.windows.x.motif
Subject: fork() and Motif: Do they mix well?
Summary: fork(), what happens to connection to the server?
Message-ID: <130@esacs.UUCP>
Date: 8 Mar 91 10:31:58 GMT
Reply-To: nick@esacs.UUCP (Nikolaos Tsivranidis(JANE))
Organization: Esa Software s.r.l. Rimini (FO), ITALY
Lines: 27


 Suppose you *have* to fork() a process and *not* do an exec(). 
 You end up with a child process that shares all the data
 of the parent (including her open file descriptors). Presumably
 you can now create a new window, and operate on the data space
 of the parent process while displaying on the windows of the
 child process.

 Questions:

 (1) This doesn't sound right to me, but I don't know exactly where
     the problems are. Is there a problem?

  (2) If one closes the Xserver connection and calls XtInitialize
      again, what happens? (If a segmentation fault produced a sound
      proportional to the seriousness of the error, how big would this
      sound be?)

  (3) If you have a lot of *application* specific data to display,
      and you would like to put the application in the background
      while displaying the data, what do you do? Remember, you only
      create the windows and display the data according to an application
      specific way.
      (If you don't understand (3) it is probably because I don't
       understand it either, this is somebody else's question.)

					- nick -