chenBright commented on PR #3309: URL: https://github.com/apache/brpc/pull/3309#issuecomment-4570843397
> Thanks. Just to confirm: with the Controller::_flags approach, set_after_rpc_resp_fn() itself becomes the opt-in signal, right? No. The set_after_rpc_resp_fn() function needs an additional parameter (default value is false). Setting this parameter to true indicates that ConcurrencyRemover covers CallAfterRpcResp. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
