o very
> important feature. Diving into the topic is welcome.
>
> -邮件原件-
> 发件人: YL G [mailto:gylg...@gmail.com]
> 发送时间: 2019年12月5日 15:33
> 收件人: dev@servicecomb.apache.org
> 主题: Re: Fw: [DISCUSSION] Rsocket
>
> According to my understanding, Rsocket and grpc are very diff
Good. Adding new programming specification for java-chassis is also very
important feature. Diving into the topic is welcome.
-邮件原件-
发件人: YL G [mailto:gylg...@gmail.com]
发送时间: 2019年12月5日 15:33
收件人: dev@servicecomb.apache.org
主题: Re: Fw: [DISCUSSION] Rsocket
According to my
According to my understanding, Rsocket and grpc are very different.
The main idea of Rsocket is stream.
In JDK, we can use CompletebleFuture to asynchronous programming.
When there is only one object like *CompletebleFuture*, it's OK.
But when we have a List, we would prefer it could like a stream:
At first glance, it looks like another gPRC but I just find this article
[1] to discuss the differences between gRPC and RSocket.
I think we need to keep eye on it.
[1]
https://medium.com/netifi/differences-between-grpc-and-rsocket-e736c954e60
yhs0092 于2019年12月4日周三 下午5:57写道：
> This is the conte
This is the content of the mail "[DISCUSSION] Rsocket is hot now" from gylgeek .
There seems some problem with his mailbox : )
Yours sincerely
Yao Haishi
yhs0...@163.com
- Forwarded Message -
From： gylg...@gmail.com
Date： 12/4/2019 17:50
To：
Subject： [DISCUSSION] Rsocket
R
