|
|
|
netchan: graceful handling of closed connection
Currently, when an importer closes the connection, the exporter gives an
error message 'netchan export: error decoding client header:EOF'. This
change causes the exporter to look for an EOF during the parse of the
header, and silences the log message in that case.
Patch Set 1 #Patch Set 2 : diff -r b1638ab4d480 https://go.googlecode.com/hg/ #Patch Set 3 : diff -r b1638ab4d480 https://go.googlecode.com/hg/ #Total messages: 4
|
gmiller
Hello golang-dev@googlegroups.com (cc: golang-dev@googlegroups.com, rog), I'd like you to review this change to https://go.googlecode.com/hg/
|
14 years, 11 months ago (2011年02月06日 22:21:32 UTC) #1 |
Hello golang-dev@googlegroups.com (cc: golang-dev@googlegroups.com, rog), I'd like you to review this change to https://go.googlecode.com/hg/
*** Submitted as http://code.google.com/p/go/source/detail?r=9f1176d9f901 *** netchan: graceful handling of closed connection Currently, when an importer closes the connection, the exporter gives an error message 'netchan export: error decoding client header:EOF'. This change causes the exporter to look for an EOF during the parse of the header, and silences the log message in that case. R=r CC=golang-dev, rog http://codereview.appspot.com/4132044 Committer: Rob Pike <r@golang.org>