kdtripathi
December 26th, 2002, 04:11 PM
I have a Pipe Server Windows Service, which starts a new thread for every incoming connection and hits specified URL with incoming data being passed to URL as query string. It collects back response from URL and writes it out to pipe connection.
From my application when I connect to pipe server and write out data, then I enter in a close loop checking after every 100 milliseconds if answer has arrived using “PeekNamedPipe”. Many times in loop “PeekNamedPipe” fails with error code “ERROR_FILE_NOT_FOUND”. When data arrives it does not fails and tells me number by bytes available that I read later which shows that connection has not been dropped. If it is failing due to fact that other end of pipe is busy doing I/O with web server then it should return back something like “Pipe not available”. In any case according to MSDN “PeekNamedPipe” should never fail rather it should come back with number of bytes available to read as 0.
My many thanks for reading post and providing any thoughts as why it could be happening?
From my application when I connect to pipe server and write out data, then I enter in a close loop checking after every 100 milliseconds if answer has arrived using “PeekNamedPipe”. Many times in loop “PeekNamedPipe” fails with error code “ERROR_FILE_NOT_FOUND”. When data arrives it does not fails and tells me number by bytes available that I read later which shows that connection has not been dropped. If it is failing due to fact that other end of pipe is busy doing I/O with web server then it should return back something like “Pipe not available”. In any case according to MSDN “PeekNamedPipe” should never fail rather it should come back with number of bytes available to read as 0.
My many thanks for reading post and providing any thoughts as why it could be happening?