May 08, 2010 05:33 PM|dotNet_Drives_Me_Crazy|LINK
Virender - thank you for your response. I am aware of both these approaches. I did consider them when looking for the right reusable components for multiple file upload. In the end, however, I ended up rejecting them.
level as well as batch level since I am anticipating upload of a lot of music files to the site, each potentially 5MB mp3. I am also looking to have the upload run in the background while the user performs other actions on the website... which means I should
be able to "minimize" the upload status area ... something that does not come out of the box in the Flash based solution offered at CodeProject.
2. The Multifile upload asp.net control has the problem that the file has to hit the server before I can even start validating it. So, for example, lets say I support only a few music file formats, I want to be able to check each file before even submitting
to the server. In case somebody want to masquerade a malicous file as mp3, I should be able to process that at the client side and reject it right there.
3. There are several jQuery file upload plugins that are Flash-independent. However, their key problem is that they rely on the HTML input (type=file) tags; some of them auto-generating multiple input tags to simulate multiple file uploads. The problem there
again is that I can't do any client side processing to make sure I shut out non-desirable files.
Another problem with existing file upload programs is that they persist the files to some server directory. I already have a SQL Server FILESTREAM setup and would like to pump the files directly into SQL Server. Now, it may be possible to point SQL Server
FILESTREAM to an uploaded file, but in all probability, SQL Server will take that file and copy it in its own area. So right there is an additional step that I want to avoid since it may add to upload times significantly.
So with these issues in mind, I started with the basics: Let's find a way of opening a dialog and accepting multiple file selections. Then, next step would be to pre-process the selected files to identify the files I really want to upload to server. Third
step--upload to the server, directly into SQL Server Database.
From what I understand I am 99% confident that the problem I am facing in the ActiveXObject is indeed a bug. I will research jQuery to understand what they do to make the multi-select dialog box open up in a cross-browser friendly way. Perhaps, I should
borrow from that code and build something on my own.
Thanks a lot for your prompt response; I appreciate your inputs and I'm sure these are the right answers that would work in some other cases, but not in mine.