The DisconnectNamedPipe function disconnects the server end of a named pipe instance from a client process.
BOOL DisconnectNamedPipe(
HANDLE hNamedPipe |
// handle to named pipe |
); |
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
If the client end of the named pipe is open, the DisconnectNamedPipe function forces that end of the named pipe closed. The client receives an error the next time it attempts to access the pipe. A client that is forced off a pipe by DisconnectNamedPipe must still use the CloseHandle function to close its end of the pipe.
When the server process disconnects a pipe instance, any unread data in the pipe is discarded. Before disconnecting, the server can make sure data is not lost by calling the FlushFileBuffers function, which does not return until the client process has read all the data.
The server process must call DisconnectNamedPipe to disconnect a pipe handle from its previous client before the handle can be connected to another client by using the ConnectNamedPipe function.
CloseHandle, ConnectNamedPipe, CreateNamedPipe, FlushFileBuffers
file: /Techref/os/win/api/win32/func/src/f17.htm, 2KB, , updated: 2000/4/7 11:19, local time: 2024/11/27 10:50,
18.188.110.150:LOG IN
|
©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://massmind.org/Techref/os/win/api/win32/func/src/f17.htm"> DisconnectNamedPipe</A> |
Did you find what you needed? |
Welcome to massmind.org! |
Welcome to massmind.org! |
.