|
|
|
|
|
|
|
|
|
 Posted: Wed Feb 24, 2010 9:13 am
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Wed Feb 24, 2010 9:32 pm
 |
|
|
 |
*throws chair* Sounds like your com is experiencing lag issues. If you use firefox, you can use some pipelining techniques.
1. Open a new tab in Firefox (Ctrl+T) and type “about:config” (without the quotes) in your address bar.
2. In the “Filter:” search box, type “network.http” (again, without the quotes.) You don’t have to hit enter.
* Look for the “network.http.keep-alive” setting and make sure it’s set to “true”. If it’s “false,” double-click that line and it will change to true.
* On the same page, look for “network.http.version” and make sure it’s set to “1.1″
3. Now clear out the Filter box and type in “pipelining”
* Look for “network.http.pipelining” Right-click on that line, and click on “toggle” and be sure the value is set to “true” (or double-click to toggle values.)
* If you’re on a proxy, look for “network.http.proxy.pipelining” Right-click on that line, and click on “toggle” and be sure the value is set to “true”. If you don’t know if you’re on a proxy or not, just set it to “true” anyway. It won’t hurt anything.
* Lastly, look for “network.http.pipelining.maxrequests” Right-click on that line, click on “modify” and set the value to 8. You can set it anywhere between 1 and 8. If you notice your internet is acting weird after this, try decreasing this value.
4. Keep in mind that this may not agree with some web servers, and therefore break the webpage. I have not personally experienced this yet, but this feature is still in testing, and that’s why it’s not set to “true” by default.
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Thu Feb 25, 2010 1:29 pm
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reply
