Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!tdatirv!sarima From: sarima@tdatirv.UUCP (Stanley Friesen) Newsgroups: comp.windows.open-look Subject: Re: Questions about the XView notifier Message-ID: <66@tdatirv.UUCP> Date: 25 Jun 91 16:02:30 GMT References: Reply-To: sarima@tdatirv.UUCP (Stanley Friesen) Organization: Teradata Corp., Irvine Lines: 30 In article etxolpn@beppe15.ericsson.se (Ola Persson) writes: >1 >How hard is the restriction "you should not use the following system calls" >, where the calls are for instance signal,system and so on? The manual uses > the same expression (you should not) when talking about some signals to avoid, > for instance SIGIO,SIGALRM and so on. These restriction are quite important - especially the rule about not using the signals. Using any of the forbidden things yourself is a good way of totally crocking the notifier. (The signals listed are critical to the internal working of the notifier and it will not work at all if it cannot get them). Since the notifier library provides an alternate interface to all of the restricted functionality, avoiding it is not a problem. >2 > >Can I always, even in the future use the notifier alone when running on > a terminal ? As far as I know, yes. The notifier is actually an independent subsystem. It does not in any way depend upon X. (It is in fact absolutely identical to the notifier that came with Sunview). I have used the notifier by itself with no problem (to write a multi-threaded network server). I find it to be a great product in and of itself. -- --------------- uunet!tdatirv!sarima (Stanley Friesen)