To optimize the website access speed, I used the DC.Web.HttpCompress compression module written by a foreigner, but the sad thing is that all the ones I found on Baidu were old versions of the original author, and there were various problems. I always like to get to the bottom of things. I think people who love technology should be like this. So I directly googled and found the latest version of the author. Although it is the latest version, it is also from 2008. However, the implementation method of this version has changed from the previous version, and I personally like this method better. After carefully reading the author's source code, I found two bugs, fixed them, and added a file caching function. Usage: 1. Upload the DC.Web.HttpCompress.dll in the file I uploaded to the bin directory of your website. Advantages: open source code, powerful customization functions, can compress a variety of resources, and can perfectly support various ajax frameworks! Disadvantages: complex to use, only supports asp.net2.0 or above! In summary, various compression Modules can optimize the page, but since the compression process occurs on the server side, enabling these compressions will consume a little server resources. However, generally speaking, compression only occurs when the client accesses the page for the first time, because After that, the browser itself caches the relationship between the page and the resource. When you refresh the access again, it will no longer occupy server resources for compression. Therefore, for developers with large website pages, enabling the compression function is definitely worth the money. , after all, the smaller the page size, the faster it will load!
Expand