tile38/vendor/google.golang.org/grpc/examples/route_guide
Josh Baker 26d0083faf Update vendoring to use golang/dep
commit a1a37d335a8e89ac89d85c00c8585d3fc02e064a
Author: Josh Baker <joshbaker77@gmail.com>
Date:   Thu Oct 5 07:36:54 2017 -0700

    use symlink instead of copy

commit 96399c2c92620f633611c778e5473200bfd48d41
Author: Josh Baker <joshbaker77@gmail.com>
Date:   Thu Oct 5 07:19:26 2017 -0700

    use dep for vendoring
2017-10-05 07:40:19 -07:00
..
client Update vendoring to use golang/dep 2017-10-05 07:40:19 -07:00
mock_routeguide Update vendoring to use golang/dep 2017-10-05 07:40:19 -07:00
routeguide Update vendoring to use golang/dep 2017-10-05 07:40:19 -07:00
server Update vendoring to use golang/dep 2017-10-05 07:40:19 -07:00
testdata Update vendoring to use golang/dep 2017-10-05 07:40:19 -07:00
README.md Update vendoring to use golang/dep 2017-10-05 07:40:19 -07: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] (https://grpc.io/docs/tutorials/basic/go.html) 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