walkero
/
nghttp2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Update REAME.rst

This commit is contained in:
Tatsuhiro Tsujikawa 2012-11-24 20:28:07 +09:00
parent 50211bc1ad
commit 58b1da39e3
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.rst
View File

@ -402,7 +402,15 @@ backend is secure SPDY proxy::
In this configuration, clients which do not support secure SPDY proxy In this configuration, clients which do not support secure SPDY proxy
can use secure SPDY proxy through ``shrpx``. Putting ``shrpx`` in the can use secure SPDY proxy through ``shrpx``. Putting ``shrpx`` in the
same box or same network with the clients, this configuration can same box or same network with the clients, this configuration can
bring the benefits of secure SPDY proxy to those clients. bring the benefits of secure SPDY proxy to those clients. Since the
maximum number of connections per server still applies in proxy
connection, the performance gain is not obvious. For example, if the
maximum number of connections per server is 6, after sending 6
requests to the proxy, client blocks further requests, which kills
performance which might be gained in SPDY connection. For clients
which can tweak these values (e.g.,
``network.http.max-connections-per-server`` in Firefox), increasing
them may improve the performance.
With ``--client`` option, it works as reverse proxy and expects that With ``--client`` option, it works as reverse proxy and expects that
the backend is SPDY-enabled Web server:: the backend is SPDY-enabled Web server::