I would be nice to gain more control over radasyncupload's upload behavior when using database as storage for uploaded files. Consider this use case. You have file management web-app that uses SQL database as storage for uploaded files. In SQL database you use Filestream enabled table to store the uploaded file data. You like to allow your app users to upload multiple big files > 100 Mt at once. And you have limited disc space on your web server hosting your app. So you don't want to buffer those uploaded files on your web server in any point of the upload process. To be able to do so radasyncupload needs to be able to stream uploaded files to the SQL database as straight as possible. Chunk by chunk. radasyncupload already has feature that allows you to use your own generic handler to handle some of the upload process. It just needs expose some of those events that happens before process-event (maybe ProcessRequest?). So developer can start handling the HttpPostedFile's InputStream at the begining of the upload and stream it directly to the database. Like one can do with the regular upload controls like so: Public Sub ProcessRequest(ByVal context As HttpContext) Implements IHttpHandler.ProcessRequest Dim hpf As HttpPostedFile For i = 0 To context.Request.Files.Count - 1 hpf = context.Request.Files.Item(i) ... Using Command As SqlCommand = New SqlCommand(String.Concat("INSERT INTO Dokuments(DokumData...) values (@DokumData...)"), connection) 'Other params Command.Parameters.Add("@DokumData", SqlDbType.Binary, -1).Value = hpf.InputStream connection.Open() Command.ExecuteScalar() connection.Close() Next End Sub
Currently the AsyncUpload saves the chunks in the Temporary folder using the original name of the file, the Process method of the Custom handler. When the Temporary folder name is very long, it can hit the Windows path length limitation of 260 symbols.
Why not add a "basic mode" to radasyncupload? that saves the selected file(s) in the target folder as soon as the upload is complete without the need for an extra postback? Or facilitate a postback through a popup "upload complete" with an ok button? And a little feedback in general on the documentation nearly all the examples have all the bells and whistles active, which makes them hard to read for programmers with little experience like me. Why not have every control with a absolutely minimalistic example that only shows the core functionality?
The RadAsyncUpload control is used on forms with other controls, and sometimes we need to validate the control, that is require that the user uploads a file before the form can be submitted. We have to use a Customvalidator and check the controls client-side properties to see if it has a file. But if you set the ControltoValidate property an exception occurs. Please support this property so that a radAsyncUpload control can be associated with an ASP.Net validator.
We would like the ability to perform drag and drop upload when using the Silverlight module. We have found and have much support from forums and posts that the FileApi module does not work with environments with Windows Authentication and IE 11. This is due to a know IE bug that is not going to be fixed. http://www.telerik.com/forums/telerik-async-upload-fails-in-ie11-on-load-balancer http://www.telerik.com/forums/radasyncupload-freezes http://www.telerik.com/forums/ie11-freezes-when-is-used-async-upload Although I can disable the FileApi, doing so prevents us from using the much loved drag and drop.
One of the issues with the asyncuploader is the inability to be able to reorder the list. There should be a way to allow for dragging and dropping the files in the desired order even after they've been uploaded to the list without having to delete the files only to upload them again in the required order.
When validation is set in order prevent a user from uploading an unsupported file, it works fine when the user uploads files with extensions. The problem is, if the same user attempts to upload from a mobile device such as from google drive, the file typically has no extensions, and therefore it fails validation; even though it in fact is a supported file. Somehow, when we know it's a mobile device, tablet, or a MAC we need to be able to allow no extensions. Create an option or detect if it is be accessed from a mobile device, and allow us to choose if we want allow files to have no extensions, even if the validation is active so that if a file is uploaded without an extension in those cases it doesn't trigger the validation and fails clients side.