Detecting EOF in Named Pipes

Hi,

I've got a problem with Named Pipe under Windows. I've created a (waiting and duplex) Named Pipe with CreateNamedPipe() and ConnectNamedPipe(). On the client side I've connected to this with CreateFile() and write an amount of data to this pipe. How can the client tell the server, that the end of data is reached. When I try SetEndOfFile() I got the error code ERROR_INVALID_PARAMETER. And closing the handle is inacceptable because after the client wrote its data, it want to read the answer, so I need the handle.

Junktyz.

Yes, SetEndOfFile only works on "real" files (that is those on a disk/memory card/tape and such). To indicate end of file on a pipe, you have two choices:
1. Close the pipe.
2. Introduce a protocol where you send the size of the file at the beginning [to make it robust, you probably need some way to ensure that the data you receive is ACTUALLY the size of the file, and not something else!]

--
Mats

I've been afraid of an answer like that . But thanks. Because the length of the data must not be known at the beginning, I implement a Brickwall Stream. The brickwall is a byte array. When closing the output stream this data is send and when reading this brickwall in the input stream, EOF is recognized.