grpc-go/examples/route_guide
Hein Meling 1ea63c9e71 Fix to avoid annoying firewall dialog on macOS (#1499)
macOS throws up an annoying firewall dialog with the following
question every time you start the route_guide/server:

Do you want the application “server” to accept incoming network connections?

This simple fix of actually typing out `localhost` seems to fix
this problem.
2017-08-31 10:24:01 -07:00
..
client Use log instead of grpclog in routeguide example (#1395) 2017-07-31 10:40:59 -07:00
mock_routeguide add license for some files (#1296) 2017-06-12 18:10:06 -07:00
routeguide go-generate pb.go files and check in Travis to make sure they don't change (#1426) 2017-08-17 16:00:51 -07:00
server Fix to avoid annoying firewall dialog on macOS (#1499) 2017-08-31 10:24:01 -07:00
testdata Add testdata package and unify testdata to only one dir (#1297) 2017-07-25 10:24:45 -07:00
README.md Canonicalize https://grpc.io as the preferred URL prefix 2017-07-10 16:28:39 -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