How do you keep a TCPClient alive.

[Darrell Sparti, MCSD]

I'm writing a remote client in C# that connects to a remote connection
manager via a TcpClient. The connection and handshake work perfectly.
I must then remain connected and respond to the connection manager's
request. I've tried calling read in a loop right after the handshake
but the first time the socket's read method is called, the socket
reports it's disconnected. I've created a TcpClientEx class inheriting
from the TcpClient and set the KeepAlive socket option but that didn't
change anything. I know the connection manager isn't closing the
connection. How can I keep the connection alive and waiting for
commands? Thanks in advance for your help!

[Sahil Malik [MVP]]

Can you send AYT (Are you there) messages?

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.ma.../13/63199.aspx
-------------------------------------------------------------------------------------------

"Darrell Sparti, MCSD" <we*******@bacausa.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...

I'm writing a remote client in C# that connects to a remote connection
manager via a TcpClient. The connection and handshake work perfectly.
I must then remain connected and respond to the connection manager's
request. I've tried calling read in a loop right after the handshake
but the first time the socket's read method is called, the socket
reports it's disconnected. I've created a TcpClientEx class inheriting
from the TcpClient and set the KeepAlive socket option but that didn't
change anything. I know the connection manager isn't closing the
connection. How can I keep the connection alive and waiting for
commands? Thanks in advance for your help!

[Darrell Sparti, MCSD]

The connection manager sends them to me and I must respond. That's why
I have to keep reading from the socket basically listening for the
server's are you there messages and responding to them. There are
other commands the server sends as well that I need to respond to.
Thanks!!!

[Darrell Sparti, MCSD]

Thank you Sahil, I found the problem. Once the connection is
established, I capture the network stream and maintain it instead of
the socket itself. The network stream manages the socket for me. I
can loop checking for CanRead and DataAvailable. When I close the
socket, the network stream is closed with it so all works fine now.
Thanks again for your help!!!!

[Darrell Sparti, MCSD]

Thanks Sahil, I figured it out. I maintain the network stream instead
of the socket. Then I just check the CanRead and DataAvailable
properties in my loop. When I finally disconnect the socket, it
automatically closes the stream for me. Thanks again for your help!!!

[Sahil Malik [MVP]]

Fantastic .. glad it worked out.

- Sahil Malik [MVP]
ADO.NET 2.0 book -
http://codebetter.com/blogs/sahil.ma.../13/63199.aspx
----------------------------------------------------------------------------

"Darrell Sparti, MCSD" <we*******@bacausa.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...

Thanks Sahil, I figured it out. I maintain the network stream instead
of the socket. Then I just check the CanRead and DataAvailable
properties in my loop. When I finally disconnect the socket, it
automatically closes the stream for me. Thanks again for your help!!!