Http/2 is the next version of Http. It provides better performance over Http/1. Especially with high latency networks such as cellular networks.
https://en.wikipedia.org/wiki/HTTP/2
It is completely optional, meaning that everything will work properly even if the client doesn't support it.
All modern browsers support it: http://caniuse.com/#feat=http2
The next version of jServer library will support it as well.
I will explain how to configure it when it is released. It is quite simple and transparent.
Note that Http/2 will only work with SSL connections.
The server example is already running with Http/2 enabled: https://b4x.com:51041/
The following page shows the protocol: https://b4x.com:51041/manyimages
The same non-ssl page is available here: www.b4x.com:51042/manyimages
On Chrome the speed difference is significant. On Firefox the speed is more or less the same (probably because Firefox sets a higher limit to the maximum number of concurrent connections).
https://en.wikipedia.org/wiki/HTTP/2
It is completely optional, meaning that everything will work properly even if the client doesn't support it.
All modern browsers support it: http://caniuse.com/#feat=http2
The next version of jServer library will support it as well.
I will explain how to configure it when it is released. It is quite simple and transparent.
Note that Http/2 will only work with SSL connections.
The server example is already running with Http/2 enabled: https://b4x.com:51041/
The following page shows the protocol: https://b4x.com:51041/manyimages
The same non-ssl page is available here: www.b4x.com:51042/manyimages
On Chrome the speed difference is significant. On Firefox the speed is more or less the same (probably because Firefox sets a higher limit to the maximum number of concurrent connections).