Killing a Secondary Thread
PP mail system -- LAWSONW@sydney.ccur.com Tuesday, February 20, 1996 G'Day! Well, in 16-bit MFC 1.5+ there are no threads, but there is a "PostRegisteredMessage" for inter-application communication. Offers the advantage of something akin to an interrupt-driven interprocess protocol rather than polling a semaphore. I'd be interested to know if "Post etc." is generic, or restricted to Windows 3.1. Regards, Jim Lawson Williams (lawsonw@sydney.ccur.com)
Mike Blaszczak -- mikeblas@interserv.com Tuesday, February 20, 1996 On Tue, 20 Feb 1996, PP mail systemwrote: >Well, in 16-bit MFC 1.5+ there are no threads, but there is a >"PostRegisteredMessage" for inter-application communication. >Offers the advantage of something akin to an interrupt-driven >interprocess protocol rather than polling a semaphore. It's a distant kin! Posting messages does _not_ interrupt the target process; the target process must still poll the message queue if it wants to eventually get the message. The message won't be delivered until the polling happens. >I'd be >interested to know if "Post etc." is generic, or restricted to >Windows 3.1. There is no PostRegisteredMessage() function in the Win32 API. .B ekiM -- TCHAR szDisc[] = _T("These words are my own; I do not speak for Microsoft.");
Roy Browning -- ctf@friday.houston.net Friday, February 23, 1996 At 09:13 AM 2/20/96 +0000, you wrote: >G'Day! >Well, in 16-bit MFC 1.5+ there are no threads, but there is a >"PostRegisteredMessage" for inter-application communication. >Offers the advantage of something akin to an interrupt-driven >interprocess protocol rather than polling a semaphore. I'd be >interested to know if "Post etc." is generic, or restricted to >Windows 3.1. >Regards, >Jim Lawson Williams (lawsonw@sydney.ccur.com) Jim; I just implemented an "Event Logger" that used that technique to allow 16-bit applications to communicate with a 32-bit application under Windows NT 3.51. Thus you may assume it is generic to all the current Windows' operating systems. A 'registry key' must be used to create a 'registered' user defined message. Also you must implement an PreTranslate member function in order to process the message. The technique isn't similar to an interrupt service rather consider the receiving process to be 'receiver' driven. In other words the process is idle until a message arrives in it's que. Roy Browning //////////////////////////////////////// C o n t r o l l i n g the F u t u r e Software Design & Development 800-CTF-0032 Roy Browning - ctf@sccsi.com ///////////////////////////////////////
| Вернуться в корень Архива |