| From: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
|---|---|
| To: | 'Magnus Hagander' <mha(at)sollentuna(dot)net>, Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: Win32 signal code - first try |
| Date: | 2004-01-11 00:46:45 |
| Message-ID: | A02DEC4D1073D611BAE8525405FCCE2B55F249@harris.memetrics.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
[oops. I missed this question]
> >1) Named pipe server creates new thread on receipt of signal
> I'm assuming you read the signal number somewhere in between here?
> Before the WriteFile, no?
Yep. The ReadFile section, to pull the signal number, wouldn't change (ie.
just how you've got it), so I didn't bother mentioning it. It would then
fire a thread to do the signal queuing, and, if the thread gets created ok,
WriteFile to release the waiting raise/kill.
Cheers,
Claudio
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-01-11 13:05:41 | Re: Win32 signal code - first try |
| Previous Message | Claudio Natoli | 2004-01-11 00:43:32 | Re: Win32 signal code - first try |