[go-nuts] Re: After conn.Close, connections is still alive

2017-03-07 Thread Allan
Yes, you're right. Thannk you. 在 2017年3月8日星期三 UTC+8上午12:05:33,Howard C. Shaw III写道: > > io.Copy is going to read from one stream and write to the other, until the > read stream is closed. "Copy copies from src to dst until either EOF is > reached on src or an error occurs." So until you close

[go-nuts] Re: After conn.Close, connections is still alive

2017-03-07 Thread howardcshaw
io.Copy is going to read from one stream and write to the other, until the read stream is closed. "Copy copies from src to dst until either EOF is reached on src or an error occurs." So until you close the stream on your side (i.e. end the telnet session), your Go code is still sitting at that

[go-nuts] Re: After conn.Close, connections is still alive

2017-03-07 Thread Christian Joergensen
On Tuesday, March 7, 2017 at 2:32:50 PM UTC+1, 倪彦春 wrote: > > I don't understand why the connection at clinet side is not closed after > `c.Close()` ? > When do you expect c.Close() to be called? Is it called then? Cheers, Christian -- You received this message because you are subscribed to