קרדיט ל-peacock על ההסבר!
אנחנו בעצם משנים את הגדרות פרוטוקול ה-http (זהו פרוטוקול המשמש לעיון באתרי www ברשת ) , הפרוטוקול מוגדר כך שלקוח יכול לפתוח עד שתי התקשרויות לשרת בזמן נתון ,לבעלי פס רחב שינוי ההגדרות הללו יכול לעזור אבל לא בצורה דרסטית ! כמו כן רק בשביל הידע הכללי שינוי ההגדרות הוא הפרה של חוקי האינטרנט . הסבר יותר מפורט באנגלית: One setting which can pay off for web browsing is MaxConnectionsPerServer. The HTTP 1.1 spec states that a client can only open up to two connections to a web server at a given time. If you change this setting, you can ramp that up -- the recommended upper limit for this is 4 -- but it won't make bandwidth magically appear. This is a recommended change for people on a good broadband connection, since it will allow you to make better use of the bandwidth you do have. Be warned that there may be web servers out there programmed not to allow more than two connections as a way of enforcing the spec and preventing connection-hogging.
Why is this useful? For one thing, whenever we load a web page, the browser usually makes one connection to download the text of the page itself -- i.e. the .HTML file -- and another connection to fetch the images. If there are a lot of images, they load one at a time, and even on a fast connection this can take time. A machine with a high MaxConnectionsPerServer can open multiple connections to the remote server and download more than one image at a time, completing the page faster. (This is, of course, assuming the remote server accepts more than two connections from a single host.) If nothing else, it's worth trying, especially on a fast connection
This procedure is for informational purposes only.
Changing the maximum number of connections beyond two is a violation of Internet standards; Microsoft does not recommended this procedure for use outside closed networks
גירסת הדפסה
סגן המנהל
מפקח
Winner
צל"ש
מומחה
