Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling handleRPC with context derived from the original #1227

Merged
merged 2 commits into from
May 11, 2017

Conversation

menghanl
Copy link
Contributor

@menghanl menghanl commented May 9, 2017

So that the context for stats handlers will have the other information as normal contexts.

Also added FailFast to TagInfo in case stats handlers care about FailFast but don't want to handle begin stats.

@menghanl menghanl changed the title Calling handleRPC with different context derived from the original Calling handleRPC with context derived from the original May 9, 2017
@menghanl menghanl requested a review from dfawley May 9, 2017 22:09
}

// RPCTagInfo defines the relevant information needed by RPC context tagger.
// FailFast is only valid on client side, it's always false on server side.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be more appropriate to document this on the field than on the struct.

How far do we think we will be extending this struct? Would it make sense to have sub-structures for client- and server- only fields?

@menghanl menghanl merged commit 17760cf into grpc:master May 11, 2017
@menghanl menghanl deleted the add_failfast_to_taginfo branch May 11, 2017 00:56
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants