M&H Systems |
Home
You may ask that if we can load the jQuery file from our own server, why load it from the CDNs. The answer is logical and very simple. The browser behavior is that whenever it loads any webpage, it keeps related files (e.g., JavaScript file, CSS file and Images) used for that page into its cache (also called history). When next time the user browses any web page, browser loads only those files that are new or modified and is not available in the browser cache or history. In this way, browser improves its performance and loads the page. The possibility is that if more and more websites are using CDNs, the user might have already browsed some other web pages that are using CDNs jQuery file and that file may have into browser cache; so when user browses your page and you are also using CDNs file, the older cached version of jQuery file will be used. In this way, your page will load faster as browser will not have to load the jQuery file for your page again.
You may ask that if we can load the jQuery file from our own server, why load it from the CDNs. The answer is logical and very simple. The browser behavior is that whenever it loads any webpage, it keeps related files (e.g., JavaScript file, CSS file and Images) used for that page into its cache (also called history). When next time the user browses any web page, browser loads only those files that are new or modified and is not available in the browser cache or history. In this way, browser improves its performance and loads the page. The possibility is that if more and more websites are using CDNs, the user might have already browsed some other web pages that are using CDNs jQuery file and that file may have into browser cache; so when user browses your page and you are also using CDNs file, the older cached version of jQuery file will be used. In this way, your page will load faster as browser will not have to load the jQuery file for your page again.
You may ask that if we can load the jQuery file from our own server, why load it from the CDNs. The answer is logical and very simple. The browser behavior is that whenever it loads any webpage, it keeps related files (e.g., JavaScript file, CSS file and Images) used for that page into its cache (also called history). When next time the user browses any web page, browser loads only those files that are new or modified and is not available in the browser cache or history. In this way, browser improves its performance and loads the page. The possibility is that if more and more websites are using CDNs, the user might have already browsed some other web pages that are using CDNs jQuery file and that file may have into browser cache; so when user browses your page and you are also using CDNs file, the older cached version of jQuery file will be used. In this way, your page will load faster as browser will not have to load the jQuery file for your page again.
You may ask that if we can load the jQuery file from our own server, why load it from the CDNs. The answer is logical and very simple. The browser behavior is that whenever it loads any webpage, it keeps related files (e.g., JavaScript file, CSS file and Images) used for that page into its cache (also called history). When next time the user browses any web page, browser loads only those files that are new or modified and is not available in the browser cache or history. In this way, browser improves its performance and loads the page. The possibility is that if more and more websites are using CDNs, the user might have already browsed some other web pages that are using CDNs jQuery file and that file may have into browser cache; so when user browses your page and you are also using CDNs file, the older cached version of jQuery file will be used. In this way, your page will load faster as browser will not have to load the jQuery file for your page again.
You may ask that if we can load the jQuery file from our own server, why load it from the CDNs. The answer is logical and very simple. The browser behavior is that whenever it loads any webpage, it keeps related files (e.g., JavaScript file, CSS file and Images) used for that page into its cache (also called history). When next time the user browses any web page, browser loads only those files that are new or modified and is not available in the browser cache or history. In this way, browser improves its performance and loads the page. The possibility is that if more and more websites are using CDNs, the user might have already browsed some other web pages that are using CDNs jQuery file and that file may have into browser cache; so when user browses your page and you are also using CDNs file, the older cached version of jQuery file will be used. In this way, your page will load faster as browser will not have to load the jQuery file for your page again.
Developers
Contact