You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicecomb.apache.org by Zhang Qi <to...@gmail.com> on 2017/12/25 09:17:03 UTC
Supporting HTTP2 for IPC
hi There,
Connection reusing is supported In HTTP2. In theory, those service2service
communication which may need some time to address in provider side may be
benefit and improve the total TPS than HTTP1 since in HTTP1, the connection
will be in waiting status before provider response.
I want to know your idea on this feature.
Thanks
Re: Supporting HTTP2 for IPC
Posted by Zhang Qi <to...@gmail.com>.
I am thinking of the scenario that the logic in service provider side is
costly. Then this connection will be reusable by other requests. This may
improve the total TPS I think. @JiMin, do you have any ideas on that?
2017-12-27 19:20 GMT+08:00 bismy <bi...@qq.com>:
> For performance, http2 cannot be faster than highway. But it has some new
> features to support mobile communication. The bad news is It is not proven
> to be better than http. It will take time
>
>
> ------------------ Original ------------------
> From: Willem Jiang <wi...@gmail.com>
> Date: 周一,12月 25,2017 9:28 下午
> To: dev <de...@servicecomb.apache.org>
> Subject: Re: Supporting HTTP2 for IPC
>
>
>
> HTTP 1.0 has Keep Alive which could save lots of connection time when the
> client server have multiple interaction.
>
> HTTP 2.0 supports to send multiple requests and response binary frames in a
> single TCP connection, but I don't think we can get lots performance
> improvement there, as our client/service network latency is not as big as
> the browser and web server, and we normally don't sent multiple requests at
> the same time.
>
> Just my 2 cents, what do you think?
>
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Dec 25, 2017 at 5:17 PM, Zhang Qi <to...@gmail.com> wrote:
>
> > hi There,
> > Connection reusing is supported In HTTP2. In theory, those
> service2service
> > communication which may need some time to address in provider side may be
> > benefit and improve the total TPS than HTTP1 since in HTTP1, the
> connection
> > will be in waiting status before provider response.
> >
> > I want to know your idea on this feature.
> >
> > Thanks
> >
>
--
张琦
Mobile:15901162453
MSN:todayhill@hotmail.com
Blog:www.faquir.net
Weibo: www.weibo.com/todayhill
Re: Supporting HTTP2 for IPC
Posted by bismy <bi...@qq.com>.
For performance, http2 cannot be faster than highway. But it has some new features to support mobile communication. The bad news is It is not proven to be better than http. It will take time
------------------ Original ------------------
From: Willem Jiang <wi...@gmail.com>
Date: 周一,12月 25,2017 9:28 下午
To: dev <de...@servicecomb.apache.org>
Subject: Re: Supporting HTTP2 for IPC
HTTP 1.0 has Keep Alive which could save lots of connection time when the
client server have multiple interaction.
HTTP 2.0 supports to send multiple requests and response binary frames in a
single TCP connection, but I don't think we can get lots performance
improvement there, as our client/service network latency is not as big as
the browser and web server, and we normally don't sent multiple requests at
the same time.
Just my 2 cents, what do you think?
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Dec 25, 2017 at 5:17 PM, Zhang Qi <to...@gmail.com> wrote:
> hi There,
> Connection reusing is supported In HTTP2. In theory, those service2service
> communication which may need some time to address in provider side may be
> benefit and improve the total TPS than HTTP1 since in HTTP1, the connection
> will be in waiting status before provider response.
>
> I want to know your idea on this feature.
>
> Thanks
>
Re: Supporting HTTP2 for IPC
Posted by Willem Jiang <wi...@gmail.com>.
HTTP 1.0 has Keep Alive which could save lots of connection time when the
client server have multiple interaction.
HTTP 2.0 supports to send multiple requests and response binary frames in a
single TCP connection, but I don't think we can get lots performance
improvement there, as our client/service network latency is not as big as
the browser and web server, and we normally don't sent multiple requests at
the same time.
Just my 2 cents, what do you think?
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Dec 25, 2017 at 5:17 PM, Zhang Qi <to...@gmail.com> wrote:
> hi There,
> Connection reusing is supported In HTTP2. In theory, those service2service
> communication which may need some time to address in provider side may be
> benefit and improve the total TPS than HTTP1 since in HTTP1, the connection
> will be in waiting status before provider response.
>
> I want to know your idea on this feature.
>
> Thanks
>