To answer OpaQue's question, since no one else seems likely to, here is what each preference does:
network.http.max-connections: This determines the maximum number of connections firefox will make to the outside world. So if you set it to one, you should only really be able to load one page at a time
network.http.max-connections-per-server: This determines how many connections firefox will make to each server. In some cases creating more connections to one server means pages can be loaded in pieces, or two pages in a framed page can be loaded at once.
network.http.max-persistent-connections-per-server: This determines how many connections to each server can be left open once a job is finished, so for example a java applet connecting to the server and maintaining the connection.
network.http.pipelining: Even though we have told firefox it may make more than one connection to each server, it will only actively use one connection at a time, although others may be open, and it may switch back and forth between connections to give an appearance of using them all. Pipelining allows firefox to use all the connections at once.
network.http.pipelining.maxrequests: This tells firefox the maximum number of requests it can actively use at once when pipelinig.
network.http.proxy.pipelining: This tells firefox it may pipeline through a proxy. Otherwise, if a proxy is set up it will not pipeline.
And finally, the new one added in a later post:
browser.cache.memory.capactiy: This sets a maximum on the amount of memory that Firefox may have allocated to it.
~Viz
Comment/Reply (w/o sign-up)