Dead Streams?
Dead Streams?
- Subject: Dead Streams?
- From: "Michael Purdy" <email@hidden>
- Date: Tue, 16 Nov 2004 09:40:27 -0500
I've noticed in the Echo Client example project a comment block
indicating streams can go dead and dead streams will not be realized
until trying to write to it. I'm confused as to why this would happen.
I guess I'm wondering what would cause a stream to go dead, beyone a
physical network issue. Is there an issue with the API that does not
allow streams and sockets to remain open?
My app needs to open a socket and keep it opened indefinitely while
data is continually sent back and forth to and from a server. Is there
a way to reconnect the socket/stream if it goes dead without incurring
much overhead (so as to not affect the real time processing needs of my
app)?
Michael
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden