We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a ticket to extend DUBBO's implicit parameter mechanism described in current DUBBO documentation: http://alibaba.github.io/dubbo-doc-static/User+Guide-zh.htm#UserGuide-zh-%E9%9A%90%E5%BC%8F%E4%BC%A0%E5%8F%82
In-short, the pattern of the above document is: [consumer side] set attachments ----> [provider side] get attachments
this ticket is intended to extend this mechanism to: [provider side(before return)] set attachments --> [consumer side] get attachments
provider side
public class XxxServiceImpl implements XxxService { public void xxx() { // 服务方法实现(service implementation) // .... // 返回之前 (before return) RpcContext.getContext().setAttachment("userToken", "0001"); } }
consumer side
xxxService.xxx(); String userToken = RpcContext.getContext().getAttachment("userToken");
The text was updated successfully, but these errors were encountered:
Could you share us the scenario about using RpcContext attachment to return results?
RpcContext attachment
Sorry, something went wrong.
Hi, I think the scenario is described in #68
@ludvik This feature is provided in 2.6.3, which is on the releasing vote thread.
&READY-TO-CLOSE&
chickenlj
No branches or pull requests
This is a ticket to extend DUBBO's implicit parameter mechanism described in current DUBBO documentation:
http://alibaba.github.io/dubbo-doc-static/User+Guide-zh.htm#UserGuide-zh-%E9%9A%90%E5%BC%8F%E4%BC%A0%E5%8F%82
In-short, the pattern of the above document is:
[consumer side] set attachments ----> [provider side] get attachments
this ticket is intended to extend this mechanism to:
[provider side(before return)] set attachments --> [consumer side] get attachments
provider side
consumer side
The text was updated successfully, but these errors were encountered: