🚀 go-pugleaf

newbie wrote:

> As implemented, ConnectNamedPipe waits for a client 
>to connect, however this locks the application which prevents 
>the user from closing or any other actions. I assume this would 
>also prevent me from closing or restarting a service aswell.

Yes, as long as you are using blocking code, it will block.
There are 4 ways to use this, but only 3 work.

1) Fully blocking
CreateNamedPipe in blocking mode.
ConnectNamedPipe( hP, NULL )

2) Asynchronous
CreateNamedPipe in blocking mode.
ConnectNamedPipe( hP, &Overlap )
WaitForSingleObject( event flag in Overlap, timeout)

3) Error
CreateNamedPipe in non-blocking mode.
ConnectNamedPipe( hP, NULL )
Must use Overlap on non-blocking pipe.

4) Asynchronous
CreateNamedPipe in non-blocking mode.
ConnectNamedPipe( hP, &Overlap )
WaitForSingleObject( event flag in Overlap, timeout)

>Any suggestions on how to change, or deal with this behavior?

Use 2 or 4 (4 would likely be prefered).
You probably want one thread per pipe in addition
to the main thread that handles the UI.

If the pipe handling is short, you might get away with
one worker thread that can handle up to 64 pipes
with WaitForMultipleObjects.

The worker threads would check a global flag every
time the WaitFor times out, and gracefully close all
the pipes, and exit.