Version: (using KDE KDE 3.3.0) Installed from: Compiled From Sources I found in the http kio-slave, that HTTP 1.1 pipelining isn't yet supported in http. Is there a plane to support it in the future? Isn't it a major source of improvements with web browsing performance?
It's definitely the main thing I miss from firefox.
*** This bug has been confirmed by popular vote. ***
Ditto. It really helps on my connection, and it's painful to see Konqueror load web pages load significantly slower than Firefox.
Hi! What's the state of this wish? Will it be considered in feature releases of kde?
Yes, we have considered it and keep on considering it.
So... Will this be in KDE 5?
Is this seriously still not fixed yet in KDE 4.1? It's hard to imagine Konqueror does not use http 1.1 pipelining...
I read of a patch somewhere which implemented http pipelining for konqueror, but it didn't make much difference or worse some sites do not load. I am wondering if maybe pipelining could be enabled depending on which server is running on the server side. With polipo, the http pipelining proxy, for example handelsblatt.com looks weird, like css are not loaded; it uses IIS according to netcraft. Sites running Apache (spiegel.de, facebook.com) seem to run fine with Polipo.
a browser has to batch gets in the right sequence and wait for certain files, before including others in the page, or it'll look wrong. Certain things like CSS and JS come to mind, and have to be applied in a certain order as well. You can't just hack it in, the browser has to know it exists and be properly coded to use the feature.
Hm, I tried handelsblatt.com and it look fine here (using polipo 1.0.4). I can provide a Debian package for Debian squeeze (http://crissi.linux-administrator.com/linux/polipo/) for testing.
I use polipo 1.0.4,too. And tried it with firefox and konqueror, but handelsblatt still looks weird. Maybe Debian has some extra Patches there... or maybe i should try to compile with -O2 instead of -O3. Those are the Patches i mentioned before. http://lists.kde.org/?l=kde-core-devel&m=122722889625928&w=2 From the Discussion i get they only server whitelist?
I know that Andreas Hartmetz was working on this, not sure it's been committed though?
No, unfortunately I have not committed pipelining. Pipelining turned out to be a major headache, mainly because too many servers seem to be broken. E.g. static.flickr.com seemed to get confused by two parallel pipelines, probably due to a stupid load balancer. For this reason and others I'd also rather commit KIO connection limits (per server and per protocol) first to get a better handle on this kind of problem. Pipelining also didn't seem to have a positive impact on performance. Conventional wisdom is that it mostly helps on high latency (like mobile or maybe even modem) connections. I asked some Mozilla developers how they made pipelining reliable, and the answer was that they've actually disabled pipelining because it's too hard to get right, and the pipelining setting is ignored. If anyone wants to see the code I've written so far I can send patches.
http://operawiki.info/HttpProtocol maybe this can help, if someone tries...
(In reply to comment #14) > http://operawiki.info/HttpProtocol > > maybe this can help, if someone tries... Not really. I can read the RFCs myself, and they don't disclose how their heuristics work. I've seen that page before.