Re: HTTP2 Multiplexing

2016-05-05 Thread Muhui Jiang
Hi Thanks Valentin. I've know the principle Best Regards Muhui Jiang 2016-05-04 19:18 GMT+08:00 Valentin V. Bartenev : > On Wednesday 04 May 2016 18:50:44 Muhui Jiang wrote: > > Hi > > > > >Nginx allows multiple request and responses in multiple connections > using > >

Re: HTTP2 Multiplexing

2016-05-04 Thread Valentin V. Bartenev
On Wednesday 04 May 2016 18:50:44 Muhui Jiang wrote: > Hi > > >Nginx allows multiple request and responses in multiple connections using > >HTTP/1.x as well. HTTP/2 changes nothing here (except it uses only one > >connection, but it's not important from the basic architecture point of > >view).

Re: HTTP2 Multiplexing

2016-05-04 Thread Muhui Jiang
Hi >Nginx allows multiple request and responses in multiple connections using >HTTP/1.x as well. HTTP/2 changes nothing here (except it uses only one >connection, but it's not important from the basic architecture point of >view). If so, it seems there is no difference or improvement of the

Re: HTTP2 Multiplexing

2016-05-04 Thread Valentin V. Bartenev
On Wednesday 04 May 2016 11:25:11 Muhui Jiang wrote: > Hi > > Different from HTTP1.1 pipeline, HTTP2 allows multiple request and response > messages to be in flight at the same time. I was wondering what the > strategy Nginx adopt to implement this main feature. Nginx allows multiple request

HTTP2 Multiplexing

2016-05-03 Thread Muhui Jiang
Hi Different from HTTP1.1 pipeline, HTTP2 allows multiple request and response messages to be in flight at the same time. I was wondering what the strategy Nginx adopt to implement this main feature. Is every single stream correspond to a thread. If not, how can Nginx provide multiple parallel