hi, about https://play.golang.org/p/3S-C4BhNYa
a q&d tcp server that echoes back the inputs. it can understand few specific words such as new, kill, start, done. so one can do nc localhost 8080 kill start new to stop the remote server, restart it, open a new client. Which is unexpected, the first client connected (command&control) should have been disconnected after the kill command, but it is still there. Also, golang does not complain when the server closes/re opens, there are no error messages about a busy port. And new clients can connect. It is a great behavior, makes me think to socket_reuse, with proper error management, but it makes me wonder what happens behind the scene ? will there be a background timeout operation that will panic soon ? or any other flaws? I m also interested by a quick CR about it, if you agree to take a minute. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
