Jupload -- A review on elegant uploading
ASP.NET is really a remarkable framework with great strengths. But it also comes with a good number of limitations. The most noted among them is visible when you have to deal with File Management. When you want to setup applications like Web-Email systems where people have to attach files to be sent along with the message, there is a acute limitation on the size of the files that can be uploaded and the efficient, secure management of the system is at stake. We here try to address this situation by an elegant alternative technology framework.
The Situation
Let us consider a design like a Web email system like Inbox.com or Gmail.com which supports upto 20 MegaBytes of email attachment. The default file upload condition of ASP.NET allows upto paltry 4 MB. You can however tweak it to any extent but then you run into performance problems since ASP.NET loads the entire file into memory. That said, if you want 100 MB file upload support, the Web.Config httpruntime is to support this limit. And 10 concurrent users using this limit at the same time would mean the server is virtually of its resources and might need a reboot in the worst case.
An Elegant Solution
We have been seeing similar queries a number of times in diversified discussion forums. But I just thought let me write about a good approach that I came across without disturbing Web.config and the default settings provided by the .NET Framework and satisfying the requirement also. I came across a good applet called 'JUpload', which is an open source Java Applet from http://jupload.sourceforge.net/ It has good number of features:
1) Good Extended Dialog Box. With source also available and with a C#-like language (Java), you can comfortably customize it for your requirements. However, ensure that your redistribution and other clauses are satisfying the original license requirements.
2) Chunk Transfer: The entire file is not uploaded or transmitted to the server. The applet transmits the file in definite chunks. Every chunk carries a distinct identifer. The server can identify the chunks and suitably assemble them at the serverside with ease. By default, JUpload comes with a PHP example to substantiate and explain the serverside reassemble.
Summary
I think JUpload is a very good tool that can be used to address the ASP.NET limitation of file sizes being transmitted. One may argue regarding ActiveX but again that would be Windows and Internet Explorer only. Besides that requires privileges to install and tampering risks. Java is known for platform independance and wide acceptance. Rather than involving in empty debates let us strive to add colors to our applications by using a rich blend of technology frameworks.
|
No responses found. Be the first to respond and make money from revenue sharing program.
|