-
Well, I don't get it. As the first connection from the browser is waiting for server answer anyway I don't see why persistent connection would be slower.
Also, from this:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
it seems it's required for a compliant HTTP/1.1 client
BTW, I'm speaking of persistent connection server side ("ziproxy to webserver" to speed up caching), not client...
2009-12-31 10:35:32 UTC in ziproxy
-
stagenex committed revision 1060 to the AjaXplorer SVN repository, changing 1 files.
2009-12-30 09:35:43 UTC in AjaXplorer
-
stagenex committed revision 1059 to the AjaXplorer SVN repository, changing 6 files.
2009-12-29 13:56:35 UTC in AjaXplorer
-
Why ?
Persistent connection speeds up browsing at least 5x.
If you monitor the HTTP trafic with a tool like Wireshark, you'll see that websites that allow keep alive transfer the complete page up to 5x faster. It also decrease webserver CPU usage, and thus increase the time a webserver is able to prioritize your request.
Currently, I'm using ziproxy with my mobile phone webbrowser, and even if...
2009-12-19 10:41:28 UTC in ziproxy
-
stagenex committed revision 3 to the Don't steal my phone SVN repository, changing 6 files.
2009-12-09 18:59:43 UTC in Don't steal my phone
-
stagenex made 2 file-release changes.
2009-12-09 14:03:01 UTC in Don't steal my phone
-
stagenex made 1 file-release changes.
2009-12-09 14:00:01 UTC in Don't steal my phone
-
stagenex made 2 file-release changes.
2009-12-09 13:18:01 UTC in Don't steal my phone
-
stagenex made 1 file-release changes.
2009-12-09 13:17:01 UTC in Don't steal my phone
-
stagenex committed revision 1058 to the AjaXplorer SVN repository, changing 2 files.
2009-12-07 10:20:10 UTC in AjaXplorer
