submit questions:
If you use the ASP.NET to upload files, the server is to save the file to memory, wait until the upload is completed. If: If you upload 1G file, there will be insufficient server memory, and the performance is greatly reduced. My idea is to solve the problem by the method of saving the disk over one side, but encountering such a problem: obtained the data stream is the data stream uploaded.
----- Transportation of large files is not suitable for direct use of in ASP.NET
To write into an ActiveX control, embedded in the ASPX page
This control is completed by the file:
1. Segment the file you want to upload into a small package, the file name, Guid-1.m, Guid-2.m
2. Write the configuration file, record the file name, and the total number of packets, the size of the package
3. Control sequentially upload files, the server is determined after receiving the parameters, the total number is equal to the current few packages, combined file combination
4. Upload 1G content with Web For a long time,
ActiveX with VB is a very simple thing, there are many online, some can be used directly, and the interface is slightly modified. ----- In / Microsoft.Net/framework/machine.config file, locate maxRequestLength, change its value for the value you need, such as maxRequestLength = "10240", indicating that you can upload 10M file ----- B / S structure is difficult to implement the file renewal, if it is really slow, do not prevent a background thread to upload. ----- Individuals believe that using C / S mode uploads files, managing documents with B / S is the ultimate solution