You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brpc.apache.org by GitBox <gi...@apache.org> on 2019/04/01 04:35:27 UTC

[GitHub] [incubator-brpc] altkatz opened a new issue #711: How to implement interceptor(or middleware)-like functionality before or after each rpc call?

altkatz opened a new issue #711: How to implement interceptor(or middleware)-like functionality before or after each rpc call?
URL: https://github.com/apache/incubator-brpc/issues/711
 
 
   **Is your feature request related to a problem? (你需要的功能是否与某个问题有关?)**
   
    I'm implementing a service which contains 8 rpc calls, and i want to do something (auth, logging, tracing, etc) before / after each of these rpc calls, how should i do that ? A similar issue already existed in grpc https://github.com/grpc/grpc/issues/9035 
   
   **Describe the solution you'd like (描述你期望的解决方法)**
   How to do it in a clean and safe way?
   
   **Describe alternatives you've considered (描述你想到的折衷方案)**
   Currently I'm considering sub-classing brpc::ClosureGuard and add logging/tracing logic there, but is that even possible ?, if so, is it safe?
   
   **Additional context/screenshots (更多上下文/截图)**
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org