Dumping a whole bunch of state into a `Context` struct is an code smell. If you can't think of a better name than context, then it is probably a poor abstraction.
-
-
We may need to keep a reference to `Context` inside middleware, but for most people they'll be able to think about "request goes in, response goes out" inside an async + fallible context. Not sure how this would apply for tikv; but this is what I'm thinking for Tide!
-
This sounds like a good step forward! We have contexts in some of our grpc requests... But I'm not really sure where or how we can improve the way we work with them. We also need to navigate a lot of languages. For the user, they don't really see the contexts.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
How are you planning to resolve it?