I'm talking to a freenet-to-http gateway that is by its nature somewhat sluggish. So I open several windows or tabs to load different pages, some of them containing a couple of images. I'm currently running into network.http.max-persistent-connections-per-server all the time: one page has, say 10 images to load, and this completely hogs the allowed connections to the gateway, blocking progress for any other pages accessed through it in the meantime. I think it would be more logical if this (and probably the other) connection limit were per tab. IMO each tab should act more like a separate browser instance. Of course this will enable users to put more load on servers by opening gazillions of windows, but, well, they'll get what they paid for. This may also cure the problems with SOAP reported in #132816 and friends, unless the SOAP applications are all on the same page.
the plan is to make the transaction queue smarter, so as to give a better priority distribution. the number of connections does not need to be increased to solve the bug you describe. bug 170668 has related comments.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
Ok. Could you give me a bug number for the queue enhancements so that I can track their progress?
see bug 142255
Status: RESOLVED → VERIFIED
QA Contact: httpqa → junruh
You need to log in before you can comment on or make changes to this bug.