3 ms·
That’s a very big assumption, at least for Go based applications.
by camel_gopher 3y ago
That’s a very big assumption, at least for Go based applications.
- edenfed 3y agoWe also thinking on implementing fallback mechanism to automatically propagate context on the same goroutine if context.Context is not passed
- nulld3v 3y agoI 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.
- otterley 3y agoTrue 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.