Re: Win32 signal code - first try - Mailing list pgsql-hackers-win32

From Claudio Natoli
Subject Re: Win32 signal code - first try
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B55F24F@harris.memetrics.local
Whole thread Raw
List pgsql-hackers-win32

> But if we are going to create a separate thread, why not do the
> ReadFile() in the new thread as well? That will make the listening part
> completely immune to any "lockups" from the client side as well (say the
> client locking up for some reason *before* sending the signal number.
> This should normally not happen, and since it's really a single API call
> I have a hard time seing how, but if we're gonig to take the step of
> creating a separate thread, let's go all the way).

Sure, but like you say, having this "lockup" is hard to imagine...

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>

pgsql-hackers-win32 by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: Win32 signal code - first try
Next
From: "Merlin Moncure"
Date:
Subject: Re: Win32 signal code - first try