qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-15 11:20:30 -07:00
Code Releases Activity

[release-branch.go1] net/rpc: fix typo in documentation, clarify semantics of error return

Browse Source 
««« backport ef713d7587f2
net/rpc: fix typo in documentation, clarify semantics of error return

Several of my students were confused by trying to use both the error
return and a reply return, so I figured it was worth explicitly clarifying
that returning an error overrides the reply.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/6327051

»»»
This commit is contained in:
David G. Andersen 2012-09-22 05:53:44 +10:00 committed by Rob Pike
parent e67e930344
commit 133727bd0c
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/pkg/net/rpc/server.go
View File

@ -24,12 +24,13 @@
where T, T1 and T2 can be marshaled by encoding/gob.
These requirements apply even if a different codec is used.
(In future, these requirements may soften for custom codecs.)
(In the future, these requirements may soften for custom codecs.)
The method's first argument represents the arguments provided by the caller; the
second argument represents the result parameters to be returned to the caller.
The method's return value, if non-nil, is passed back as a string that the client
sees as if created by errors.New.
sees as if created by errors.New. If an error is returned, the reply parameter
will not be sent back to the client.
The server may handle requests on a single connection by calling ServeConn. More
typically it will create a network listener and call Accept or, for an HTTP