Upload for MVC lucks upload in chunks feature as upload for ajax. So it is impossible to upload large files (like more than technical limit for asp.net in 4Gb). In my current project with 360 degrees videos where files might be 10+ Gb it is vital.

can refer http://tus.io/demo.html for resumable file upload.
and http://www.dropzonejs.com/ for drop zone.
its beautiful and important plugin. hope fully kendo can intergrated.

The upload control takes up a lot of space on the web page when you upload a lot of files.  As each file completes, I want an easy way to remove those files.  Ideally, a configuration option to automatically remove completed files otherwise a function to remove the file from the list from within the Success event.

The Upload widget would be vastly more useful if it could upload with the  PUT as this would enable direct to S3 or GCS PUTs.

I would like to be able to use a progress bar while uploadiing files synchronous using the MVC Upload control

I would like to be able to be able to use unique filenames when uploading files asynchronous or maybe filnames based on GUID names

When we upload files with the Kendo Upload, it would be nice to upload them sequentially, in separate requests

Provide the image preview option for kendo upload.

when we want to storage files directly to Azure storage we need first to upload the files to the server and then upload from the server to the azure storage...
why there isn't an option like RadCloudUpload that support cloud storage providers ?

currently i can retrieve lastmodifieddate by using onUpload() event, but i cannot retrieve creation date. i hope kendo can update the kendo upload that can provide creationdate.

Incorporate some mechanism which will allow us to handle situations where a file is uploaded, yet the target folder already has a file with the same name.  i.e. An event that is fired we can trap which will allow us to rename the file, then save it.

i really needed Upload By Folder like goolge drive uploader. i hope kendo will add that feature.

I see in the forums you do not support what i need - but we really need it and will have to use a different control without it.  We need the ability to have the upload control, look, feel and act like it does in "Async Mode".  But when in this mode we need it to only upload 1 or two individual files at a time.  The issue is not bandwidth it is processing power.  So the "batch" trick doesn't work - we don't need all the files at once.  We need one file at-a-time, with the easy of letting the user pick a bunch and see them all listed out.  Something like

Async{  throttleLimit: 2}  - Where throttle limit simply keeps the number of pending uploads to 2 and waits until they succceed/fail to start uploading the next and so on.

In order to be able to manage files attached to server objects, it would be nice if we could bind the Upload widget to a datasource. 
The read() method of the datasource could be used to load the widget with the list of files attached to a given server object. 
The create() method would be used to upload new files to the sever.
The destroy() method would be used for deleting existing files on the server.

This would make the upload widget more consistent with other widgets like the combo boxes or the dropdown lists.

The suggested way to omit the Remove button is to not provide a Remove URL/Action.  However this breaks the list of the async upload such that the list doesn't get cleared with each new upload.  Since its an async upload that automatically uploads, there no point in accumulating a list of uploads.  Whether or not you expose a remove button shouldn't be tied in any way to the clearing of the list when a new upload is made.  That should only affect the availability of a remove button. At the very least you could provide some documentation on this quirky behavior.  Instead its random walk of, ok if I change this property what happens, how about this one, how about both, and whirl away a few hours screwing around with unpredictable behaviors.


    @(Html.Kendo().Upload()
                .Name("pdfFiles")
                .Multiple(false)
                .Async(configuration=> configuration
                    .AutoUpload(true)
                    .Save("UploadTemporaryPdf", "StatementOfCredit")
                    //.Remove("RemoveTemporaryPdf", "StatementOfCredit")
                )
                .Events(events=> events
                    .Select("onUploadSelect")
                    .Success("onUploadSuccess")                    
                    .Error("onUploadError")
                 )
                .HtmlAttributes(new { accept = "application/pdf" })

The current upload control does not allow the PUT verb. This means you cannot use it with Amazon S3 without implementing a proxy server. The problem with the proxy server approach is that it places unneeded strain on your own servers and you get charged twice for data transfer, once on the way in to the proxy server and again from the proxy server to S3.

Add support to the Upload widget to upload files to an OData service, for instance to add attachments to SharePoint list items using SharePoints OData service. 

At the same time it would be good to be able to specify the urls for the Upload widget in an upload-datasource in a view model to which the Upload widget is databound, basically separate the uploading from the widget. That way you can choose to use an OData upload-datasource or a multipart/form-data upload-datasource. Obviously this OData upload-datasource may only be supported in browsers that support the HTML5 file api.

It would be nice to have xhr in upload's remove event handler since sometimes we need to modify/add http headers on request.

It woudl be great if we coudl access an images dimensions on upload, to avoid having to do server trips to determine if an image is valid.

Please resolve this, as this is a pain point for our customers.