You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by "complone (GitHub)" <gi...@apache.org> on 2019/01/23 06:46:52 UTC
[GitHub] [incubator-dubbo] complone opened issue #3314: Why not
convert dubbo's futrue to callback
Since dubbo's ```futrue``` is to determine which provider is forwarded to the``` Comnsumer```, the dubbo ```callback``` function exists to solve the request to send the corresponding service, so why not directly translate``` furtrue``` into a callback?
Refernce: https://blog.csdn.net/u010317829/article/details/52151896
Doc: http://dubbo.apache.org/zh-cn/docs/dev/design.html
[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3314 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org
[GitHub] [incubator-dubbo] complone commented on issue #3314: Why not
convert dubbo's futrue to callback
Posted by "complone (GitHub)" <gi...@apache.org>.
> Since the underlying dubbo is also based on netty, I think we should make full use of the futrue/promise mode to give network performance optimization problems to netty.
>
> The reason why dubbo uses futrue for asynchronous calls, isn't it because of the NIO mechanism?
https://www.cnblogs.com/tiancai/p/9573912.html
[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3314 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org
[GitHub] [incubator-dubbo] complone commented on issue #3314: Why not
convert dubbo's futrue to callback
Posted by "complone (GitHub)" <gi...@apache.org>.
I have seen that the return value of callback is handled in Dubbo 2.7 using the JDK native interface.
[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3314 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org
[GitHub] [incubator-dubbo] complone commented on issue #3314: Why not
convert dubbo's futrue to callback
Posted by "complone (GitHub)" <gi...@apache.org>.
Since the underlying dubbo is also based on netty, I think we should make full use of the futrue/promise mode to give network performance optimization problems to netty.
The reason why dubbo uses futrue for asynchronous calls, isn't it because of the NIO mechanism?
[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3314 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org