#CLIENT->SERVER Problem
4 messages in this thread
SysOp,
I seem to be having a problem with PIPES. This is what I am doing
I open the SERVER:
CreateNamedPipe("me",
PIPE_ACCESS_INBOUND | FILE_FLAG_OVERLAPPED,
PIPE_READMODE_MESSAGE | PIPE_NOWAIT |
PIPE_TYPE_MESSAGE,
50,
32000,
32000,
0,
NULL);
ConnectNamedPipe(…)
This allows the server to continue processing while the Client is
starting or vice versa.
Then the CLIENT starts:
CreateFile("me",
GENERIC_WRITE,
FILE_SHARE_READ | FILE_SHARE_WRITE,
NULL,
OPEN_ALWAYS,
FILE_FLAG_OVERLAPPED,
NULL);
I then attach an event to the OVERLAPPED structure.
This all works as planned – I can send from the CLIENT to the SERVER
with no problems. BUT if I stop the CLIENT either controlled(
closing handles) or just stop the process. The next time it starts
at the CreateFile returns the error 231(ERROR_PIPE_BUSY)!!!!!
Is this a bug – or is there some other way to accomplish this affect?
THANX in advance
Bill Whitman
There is 1 Reply.
The Win32 API Helpfile states that the pipename must be of the form
(in C syntax) "\\\\.\\pipe\\name" and not just ""name". You should probably
change your code to conform to that. Also, creating named pipes is not
supported in Win32s, so you should probablytake this question to Section 6,
API-Base/Console.
Thanks.
Lee
There is 1 Reply.
Lee,
I used the correct format for the named pipes ("\\\\. blah blah)
I just used this format for implicity sake.
I did put this question on the Base\console about a week ago,
with no reply.
I really need this functionally!!! and need to know what is
the problem with my code.
THANX again
Bill Whitman
There is 1 Reply.
Wiliam,
Sorry for the delay in getting to this. Would it be possible to
upload a small program displaying this behaviour to lib. 6?
It would really help me narrow down what is wrong quickly.
We can pick this up in Base/Console again.
-Rohan