have anyone noticed...

[HeavenAgain]

go to address bar, and type in about:config
and scroll down a bit, you'll see network.http.pipelining, by default its set to false, if you change it to true... wouldnt your loading speed be faster?
and i think this only works on firefox, havnt tried with others yet...

[Dan]

about:config is the setings page for firefox so i am prity shure it will not work in others unless there code is based off of firefox. (or firefox is based off there code)

For more info on what pipelining is check out http://kb.mozillazine.org/Network.http.pipelining


As with most things in life it has it's pros and cons.

[HeavenAgain]

Quote:

Users who want better page loading speed can try setting this preference to true, keeping in mind this may break some websites.

well, who wouldn't want faster loading speed, as long it doesnt break my computer AND compsci.ca then im fine with that

[Dan]

It can also put more load on webpages as it makes more calls to them (using up more instances of the server software) so it can be bad etiquette if you set it to to many pielines.

Also some sites and services check how many of the same IP are connected at once and will kill off new connections if to many of the same IP are requesting at the same time, so this could make things kind of messed up if you only get a fraction of the page.

Finaly it can also screw up sties stats making a view for each pieline you use rather then just one.

Personaly i do not care as the webmaster of compsci.ca but other webmasters might.

[PaulButler]

Dan @ Wed Nov 28, 2007 11:37 pm wrote:

It can also put more load on webpages as it makes more calls to them (using up more instances of the server software) so it can be bad etiquette if you set it to to many pielines.

Also some sites and services check how many of the same IP are connected at once and will kill off new connections if to many of the same IP are requesting at the same time, so this could make things kind of messed up if you only get a fraction of the page.

Finaly it can also screw up sties stats making a view for each pieline you use rather then just one.

Personaly i do not care as the webmaster of compsci.ca but other webmasters might.

Actually, from the link posted above, it sounds like HTTP pipelining is just passing multiple requests before receiving the response.

For example, an HTTP 1.0 request:

code:

GET /page.html HTTP/1.0 [server sends response]

An HTTP 1.1 request with keep-alive:

code:

GET /page.html HTTP/1.1 [server sends response] GET /favicon.ico HTTP/1.1 [server sends response]

An HTTP 1.1 request with pipelining:

code:

GET /page.html HTTP/1.1 GET /favicon.ico HTTP/1.1 [server sends page.html] [server sends favicon.ico]

That's the impression I got from reading the page anyway, I could be wrong.

[Dan]

In the HTTP 1.1 with keep-alive thos requests are done one affter another so they only need one instance of the web server per person doing the requesting. However with pipelineing it makes muptial requests almost at the same time so it will spaw muptial instnstces of the server software server side to deal with muptial requests at the same time.

This is what i ment and how i blive it will work.