1
0
mirror of https://github.com/golang/go synced 2024-11-19 14:14:40 -07:00

http: document that ServerConn and ClientConn are low-level

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/4635081
This commit is contained in:
Brad Fitzpatrick 2011-06-29 18:23:38 -07:00
parent 121775f2c8
commit d980f538d7

View File

@ -24,6 +24,9 @@ var (
// to regain control over the connection. ServerConn supports pipe-lining,
// i.e. requests can be read out of sync (but in the same order) while the
// respective responses are sent.
//
// ServerConn is low-level and should not be needed by most applications.
// See Server.
type ServerConn struct {
lk sync.Mutex // read-write protects the following fields
c net.Conn
@ -211,6 +214,9 @@ func (sc *ServerConn) Write(req *Request, resp *Response) os.Error {
// connection, while respecting the HTTP keepalive logic. ClientConn
// supports hijacking the connection calling Hijack to
// regain control of the underlying net.Conn and deal with it as desired.
//
// ClientConn is low-level and should not be needed by most applications.
// See Client.
type ClientConn struct {
lk sync.Mutex // read-write protects the following fields
c net.Conn