Named Pipes

[Mufasa]

I'm trying to get Named Pipes working. It works fine as long as the server
is up and going. Once I stop the server, the client doesn't notice the
server isn't there on the first message, which is lost but then it notices
that the pipe is down.

Anybody have any code they could post or a link to it?

TIA - Jeff.

[Peter Duniho]

On Mon, 28 Jul 2008 11:53:24 -0700, Mufasa <[e-mail]:

I'm trying to get Named Pipes working. It works fine as long as the
server
is up and going. Once I stop the server, the client doesn't notice the
server isn't there on the first message, which is lost but then it
notices
that the pipe is down.

What do you mean by "on the first message"? Sent from the server to the
client? Or the other direction? How are you using the pipe? How are you
detecting the error?

For what it's worth, TCP/IP won't detect an error until you try to send
data. A synchronous, non-blocking send will generally result in an error
if the connection has been broken, but I suppose it's possible that the
named pipe implementation is somehow deferring that error for some reason,
or that you are using the named pipe in some other way.

Anybody have any code they could post or a link to it?

It seems to me that your best bet is to share _your_ code and be more
specific about what is and isn't working for you. Please make sure that
any code sample is both complete and concise.

Pete