Comments

TheHappyFriar wrote on 4/2/2005, 5:55 PM
sweet. thanks! :)
mjroddy wrote on 4/2/2005, 8:53 PM
Interesting...
I've done the tweeks - now I'll have to play around and see if I notice the dif.
Thanks for the link.
MyST wrote on 4/3/2005, 3:41 PM
Sweeeeeet!
Seems much quicker.

Thanks for that!

Mario
craftech wrote on 4/3/2005, 7:36 PM
Yes thanks,

John
scottshackrock wrote on 4/4/2005, 6:13 PM
this just in, this stuff could be bad.....haha
Buddy of mine told me this:
"It's a real good way to crash a webserver.

These are the same three config options that normally decent sites like hackaday have been regurgitating over and over and over and over for the past year. I really wish they would stop publishing the maxrequests option.

If everybody did it, the whole web would slow down.

Increasing maxrequests means that instead of one TCP session for your data, the browser attempts to make eight, or ten, or fifty simutaneous connections.

If EVERYBODY did it, you'd either get a helluva lot more connection refused messages, as admins started setting hard limits in their server configurations, or downright dead websites, as servers crashed from the load."
FuTz wrote on 4/10/2005, 4:14 PM
Did anybody ever uninstalled Firefox?
Just because some friend of mine uninstalled it and it erazed everthing from the drive where it was installed. Luckily, it was a different drive than his OS so he could use the comp'... to discover everything went away.
I do have the first version and *you bet* it's still on my system and it will remain there !


! ! ! O_O ! ! !
BillyBoy wrote on 4/10/2005, 7:26 PM
I think your friend just goofed. It makes little sense any application would wipe out a whole hard drive unless it was some malicious software to begin with pretending to be Firefox but then they usually target the root drive and earse that first.
rcrawfor42 wrote on 4/13/2005, 9:42 AM
"Increasing maxrequests means that instead of one TCP session for your data, the browser attempts to make eight, or ten, or fifty simutaneous connections."

Not in the context of "pipelining". The pipelining option is how many resources to request in the context of a single socket connection. It doesn't increase the number of sockets used. In fact, it's much, much more efficient in network load terms than the normal HTTP connection.

Your buddy confused the pipelining maxrequests with another parameter, max-connections-per-server, which COULD cause problems by using too many sockets.