home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!microsoft!hexnut!johnhall
- From: johnhall@microsoft.com (John Hall)
- Subject: Re: Thread signalling and ERROR_INTERRUPT (shades of OS2 1.3)
- Message-ID: <1992Nov09.215357.5107@microsoft.com>
- Date: 09 Nov 92 21:53:57 GMT
- Organization: Microsoft Corporation
- References: <Bx9rz8.I9t@unx.sas.com>
- Lines: 29
-
- In article sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:
- | Is there any concept of the OS/2 ERROR_INTERRUPT return code for
- | Windows NT WIN32 calls made into a blocking system call by a thread?
-
- No.
-
- | If not, how can you "wake up" a thread in a multi-threaded application
- | that happens to be blocked in a system call such as a Windows SOCKET
- | or 3270 HLLAPI call? Blowing away the thread is not an option.
- | Nor can a list of semaphores be waited on instead.
-
- The best way to do this is to have your thread wait on multiple
- objects with 'ANY' meaning only one has to be signaled for the
- wait to complete.
-
- Then, you just do a SetEvent() or some such if you want
- the attention of that thread.
-
- Signals that interrupt system calls are not supported in Windows
- NT. Nor are cross-process signals. The NT designers do not think
- that the Unix model (any system call may be interrupted at any
- time by a signal) is they way to right good, robust systems.
-
-
-
-
-
- --
- -------------------------
- My comments are my own. They are independent and unrelated to the
- views of my company , relatives or elected representatives.
-
-