undefined | Better HN

0 pointscamel_gopher2y ago0 comments

That’s a very big assumption, at least for Go based applications.

0 comments

I don't think it's unreasonable, you need a Context to make a gRPC call and you get one when handling a gRPC call. It usually doesn't get lost in between.

otterley2y ago

True for gRPC, but not necessarily for HTTP - the HTTP client and server packages that ship with Go predate the Context package by quite a long while.

edenfed2y ago

We also thinking on implementing fallback mechanism to automatically propagate context on the same goroutine if context.Context is not passed

j / k navigate · click thread line to collapse

0 comments

nulld3v2y ago

I don't think it's unreasonable, you need a Context to make a gRPC call and you get one when handling a gRPC call. It usually doesn't get lost in between.

otterley2y ago

True for gRPC, but not necessarily for HTTP - the HTTP client and server packages that ship with Go predate the Context package by quite a long while.

edenfed2y ago

We also thinking on implementing fallback mechanism to automatically propagate context on the same goroutine if context.Context is not passed

j / k navigate · click thread line to collapse