Upload Large File Client
Want to ask, what do you use to achieve file upload? Need a Web client, can upload large files, if it is FTP or other protocols need to be able to notify the HTTP server end after upload, or at least server side can have prepost events
If HTTP uploads need to be able to support chunk, hopefully a solution for HTML5 or Flash, do not Java applets or JavaFX
Don't even pay for the expensive things like aspera.
The main thing is to be able to upload large files, large files refers to the maximum up to 100G files,
Server side If you can have PHP script the best
I've tried jquery file upload and plupload.
------Solution--------------------
Recommended for use with flash+php, with third-party class libraries
------Solution--------------------
Citation:
want to ask, what do you use to achieve file upload? Need a Web client, can upload large files, if it is FTP or other protocols need to be able to notify the HTTP server end after upload, or at least server side can have prepost events
If HTTP uploads need to be able to support chunk, hopefully a solution for HTML5 or Flash, do not Java applets or JavaFX
Don't even pay for the expensive things like aspera.
The main thing is to be able to
... The traditional HTML method has been difficult to meet the large file upload. Don't say it is 100MB,50MB to the server is very large, service not only to open a socket connection has been waiting for this file upload completed, but also to allocate the same size of memory to save the file on the server caused by the pressure is quite large, And the pressure will increase with the increase of the user geometry. Even if it is not with Flash, because the current flash does not support the continuation of the breakpoint operation, also does not support file block operation, Flash and the traditional way of HTML upload principle. Upload 100MB images with flash, and the server will allocate 100MB of memory. 10 users upload 100MB data at the same time, will eat server 1G of memory.
Flash upload is the entire file is truncated into memory, this is a serious problem. Because if the user is uploading 5G files, Flash will load all 5G files into memory. This can seriously affect the user's operational experience. Because then the user's computer will be in suspended animation state. The average user's computer is also 2G, so hang up directly, out of memory, or memory overflow.
Some friends have tried to upload large files with the Flash file upload control, but often encounter upload time-outs, or upload errors. This is because the Flash file upload control now uses the same technology as the traditional HTML upload. Let the server open a connection and wait until the client has finished sending the file. However, in the actual network environment, the user's speed may be only 50kb/s, uploading 200MB files may take 2.8 hours. However, the server session connection is not possible for the user for 2.8 hours, this does not consider the complex network environment, such as packet loss situation. If you encounter packet loss and network anomalies, the 100MB file in front of the user is white. This equates to a waste of one hours of user time. Bring a very poor experience to the user.
For the server, the connection resource is very limited, even if the server can be a user for 2.8 hours, if the user access a large, each user occupied a connection and take so long, then the server's concurrency processing power is very low. Other users are asked to request a simple 1KB HTML page and must wait for the server to finish processing the previous user's request.
At the same time Flash can not meet the large file upload requirements. Because of the large file upload requirements have a requirement is to ensure the stability of data transmission. For example, the user uploads 1G files, has uploaded 500MB, then the network suddenly broke, but the user hope that the next time the file is uploaded from the location of the last upload to start the transmission, that is, from the location of the 500MB to start transmission, this demand is flash can not do.
Like QQ mailbox in the super-large attachment upload function, 115 network disk in the large attachment upload control, Huawei Network Disk (Dbank), Jinshan fast disk they are all using the control to achieve large file upload function. This is done primarily to reduce server stress (faster server response times and more concurrent processing), saving server memory (the server does not have to allocate the same size of memory to each user) while improving the user experience (users can upload oversized files in a complex network environment).
Of course, from a technical point of view, such as these internet-well-known enterprises are also considered to support the massive users of distributed file storage architecture design. Because their file storage servers cannot be one, they will dynamically increase as the number of users increases.
If it is true that some friends say that the flash control can solve the problem of large file upload, then Tencent will not spend so much effort to develop a control for the QQ mailbox specifically.
