> The client is supposed to do this automatically if I remember correctly but > there are some situations where the client does not detect that the > connection was lost. I'm not really strong in the fine points of socket > connections.
I've had the dubious pleasure of writing C++ socket code recently, and trying to make it bullet-proof, on both windows and linux. The cruel truth is the only way to reliably detect when a connection has dropped is at the protocol level: the server or client has to send a "keep-alive" message regularly; the other side has to keep track and realize when it has not received one on time. In my case I had no control over the server-side, so I had to do some tricks such as sending the data and the LF in separate commands (if the first send fails, you get an error when you try to send the LF, though even that is OS and timing dependent). However in the case of CGOS you control both sides so could easily implement some keep-alive protocol. (Wasn't there a proposal to measure network latency? It could fit in with that.) Darren -- Darren Cook, Software Researcher/Developer http://dcook.org/gobet/ (Shodan Go Bet - who will win?) http://dcook.org/work/ (About me and my work) http://dcook.org/blogs.html (My blogs and articles) _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
