Folks,

HTTP2 protocol support is quite critical to Dubbo. In the future, I hope
this support can facilitate the hand hold device talks to back end service
in the future. Pls. review it, advise it. This work can be moved into the
dubbo rpc project as a built-in extension.

Thanks,
-Ian.


On Thu, Aug 30, 2018 at 10:16 AM Zonghai Shang <[email protected]> wrote:

> Hi Jun,
>
> Develop http2 protocol to solve the following problems:
>
> 1. Preparing for future service mesh. In fact, we have used the http2
> protocol and service mesh matching internally. I wanted to use grpc's http2
> protocol, and found it difficult to adapt to the internal large-scale
> dubbo, and finally gave up.
> 2. Some scenarios are expected to support secure connections. Currently
> dubbo does not support this feature.
> 3. Http2 supports long connection multiplexing, supporting cross-language
> if cross-language serialization is used.
> 4. Http2 is compatible with most features of dubbo, such as asynchronous
> parameter callback, but currently does not support telnet
>
> I am looking forward to more dubbo enthusiasts to participate in it.
>
> Best regards,
> yiji
>
> jun liu <[email protected]> 于2018年8月30日周四 上午9:44写道:
>
> > Hi Zonghai,
> >
> > Well done!
> >
> > I think we need a detailed proposal describing your design purpose and
> why
> > Dubbo should support http2 or something like that worth explanation. That
> > would make it easier for the community to express their opinions.
> >
> > Would you like to provide a proposal?
> >
> > Best regards,
> > Jun
> >
> > > On 29 Aug 2018, at 14:17, Zonghai Shang <[email protected]> wrote:
> > >
> > > Hi All,
> > >
> > > Very happy to show the new dubbo rpc protocol - http2, new extended
> > > protocols provide secure connections, multiplexed connections,
> > asynchronous
> > > parameter callbacks, etc.
> > >
> > > http2 protocol: https://github.com/zonghaishang/dubbo-rpc-http2.git
> > > http2 example: https://github.com/zonghaishang/dubbo-example-http2.git
> > >
> > > Best regards,
> > > yiji
> >
> >
>

Reply via email to