grpc-go/examples/route_guide
Menghan Li 39333409e4
internal: copy testdata to routeguide (#2478)
So it's not necessary to set the testdata file as flag.

Without this, using relative directory, the example only works if run in `example/routeguide`.
2018-12-13 14:47:53 -08:00
..
client cleanup: replace "x/net/context" import with "context" (#2439) 2018-11-12 13:30:41 -08:00
mock_routeguide cleanup: replace "x/net/context" import with "context" (#2439) 2018-11-12 13:30:41 -08:00
routeguide internal: Update proto generated code (#2133) 2018-06-08 17:54:26 -07:00
server internal: copy testdata to routeguide (#2478) 2018-12-13 14:47:53 -08:00
testdata Add testdata package and unify testdata to only one dir (#1297) 2017-07-25 10:24:45 -07:00
README.md Fix grpc basics link in route_guide example (#1713) 2017-12-06 15:11:16 -08:00

README.md

Description

The route guide server and client demonstrate how to use grpc go libraries to perform unary, client streaming, server streaming and full duplex RPCs.

Please refer to gRPC Basics: Go for more information.

See the definition of the route guide service in routeguide/route_guide.proto.

Run the sample code

To compile and run the server, assuming you are in the root of the route_guide folder, i.e., .../examples/route_guide/, simply:

$ go run server/server.go

Likewise, to run the client:

$ go run client/client.go

Optional command line flags

The server and client both take optional command line flags. For example, the client and server run without TLS by default. To enable TLS:

$ go run server/server.go -tls=true

and

$ go run client/client.go -tls=true