QLocalServer with multiple clients — proper handling

[indiocolifa]

I think your approach is well thought, altough I don't find the difference with my multiple instances of a handler class (SocketHandler) except that it's not a socket (it does not inherit QLocalSocket) but QLocalSocket is composited as a member variable.

I believe it's not related to the disconnection (and pipe-handle leaking) problem, but who cares, I will try your idea.

[indiocolifa]

I implemented your solution, but I still keep getting pipe handles not closed.

For each connection, Qt creates the following named pipes:

\Device\NamedPipe\Win32Pipes.00001490.0000000X 
\Device\NamedPipe\<SERVER_KEY>

\Device\NamedPipe\Win32Pipes.00001490.0000000X 
\Device\NamedPipe\<SERVER_KEY>

To copy to clipboard, switch view to plain text mode 

The second that includes the server key in the pipe name is the type of pipe handles that are not closing.

May be it's an error in my client.
When my client tries to shutdown the connection, the socket error slot signals, with:

QLocalSocketPrivate::completeAsyncRead: Connection error

My client application calls _socket->disconnectFromServer() in the aboutToQuit() handler slot (prior to app quitting).

I related the problem to the eventloop not already responding on the aboutToQuit(), but I tried on other program sections, when the event loop is well alive, and it didn't work. Nevertheless, sockets will get deleted on clean program close, so I think I should not bother manually disconnecting.

[indiocolifa]

Fixed by letting the server-side closing the socket on disconnection signal. The client just does not nothing, just waits the server to close and delete the QLocalSocket pointer on disconnection.

Thanks, anyway.