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.

Sign up for GitHub

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

Jump to bottom

Invoker在返回RpcResult时添加的attachements没有传给consumer的proxy. #68

Closed
chenwmw opened this issue Jul 11, 2014 · 5 comments
Closed

Invoker在返回RpcResult时添加的attachements没有传给consumer的proxy. #68

chenwmw opened this issue Jul 11, 2014 · 5 comments

Comments

@chenwmw
Copy link

chenwmw commented Jul 11, 2014

主要想法是模仿http cookie实现servlet session的思路，通过attachement来传递session ID，藉此达到支持Session的目的，目前加在RpcInvocation attachement中的sessionID能成功的传递给provider端的Invoker，但是在调用结果封装对象RpcResult attachements的sessionID却不能穿会给consumer端的proxy factory.
@jxctx88
Copy link

jxctx88 commented Apr 17, 2017

同问，这个问题有解决吗？

@takeseem
Copy link
Contributor

takeseem commented Apr 18, 2017 •
edited
Loading

14年master分支，我们用来传递一个系统跟踪id，除了rmi协议需修复外，走dubbo协议是ok的

@jxctx88
Copy link

jxctx88 commented Apr 20, 2017

你说的应该是consumer传递给provider，我们说的是proider反传给consumer

@takeseem
Copy link
Contributor

这个倒是真的，没有反传过。

@ralf0131 ralf0131 mentioned this issue Jul 16, 2018
Closed
@ralf0131
Copy link
Contributor

dup with #448

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ralf0131 @takeseem @chenwmw @jxctx88