context.Context on the server side about grpc-go HOT 7 CLOSED

It's there. For non-streaming RPCs (e.g. https://github.com/grpc/grpc-go/blob/master/examples/route_guide/server/server.go#L75) it is the first arg. For streaming RPCs (e.g. https://github.com/grpc/grpc-go/blob/master/examples/route_guide/server/server.go#L86) it is available by calling the Context method on the stream value.

from grpc-go.

Ah. I only saw the steaming examples. Thanks for this 👍

from grpc-go.

Reopening this for a clarification.

On the client, if I do this:

ctx = ctx.WithValue(someKey, someValue)

And on the server:

value := ctx.Value(someKey)

Should I not expect to get the value back?

from grpc-go.

You should not expect that. You need to use the metadata mechanism.

from grpc-go.

I can see that a deadline set on the client gets propagated to the server. Any reason for excluding the values (apart from serialization/deserialization headaches) ?

from grpc-go.

Those are a bit more than headaches. They are major design issues. And there's only a limited set of context values that make sense to transit across machines transparently.

from grpc-go.

I just saw https://godoc.org/google.golang.org/grpc/metadata

Thanks for the clarification though :)

from grpc-go.