RadAsyncUpload utilizes four different modules for file uploading – Iframe, Flash, Silverlight and File Api. The module with highest priority is File Api. If the browser does not support File Api that module is automatically changed to Silverlight. Ifthere is no Silverlight installed on the client machine, RadAsyncUpload will utilize the Flash module. If neither Flash nor Silverlight is installed – the IFrame module takes place.
Since the three modules are based on entirely different technologies there are slight differences in the approach they handle file uploads. The following information might be useful to developers implementing RadAsyncUpload in their scenarios:
This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (e.g. with an overloaded send() method for File or Blob objects), postMessage, DataTransfer (part of the drag and drop API defined in [HTML5,])and Web Workers. Additionally, it should be possible to programmatically obtain a list of files from the input element when it is in the File Upload state[HTML5].
The new module supports the following features:
Multiple file upload
Stand alone progress monitoring(No http module used!)
Support for the same events as the other modules
Upload files via chunks, effectively walking around the ASP.NET max files size limitation.
Limitation of the File Api module:
- No file filtering, i.e. it is not possible to filter the select files dialog with the allowed extensions, because the latterfunctionality is not yet implemented by any browser. This is the only disadvantage of File API compared to Silverlight.
The File Api module is supported by the following browsers: FireFox 3.6 or grater, Google Chrome, Safari 5
The IFrame and Flash modules upload the selected file(s) using normal http post request. The iframe use <input type="file" /> tag forfile uploadswhereas Flash uses the Flex FileReference object in order to upload files. The files are uploaded using Post HTTP requestin absolutely the same manner as the normal <input type="file" /> and html form. On the server, there is no difference where you have used the normal <input type="file" /> upload or the Flash upload in order to upload the files. The files are buffered in the ASP.NET Temporary folder,not in the App_Data/RadUploadTemp folder. After the upload is completed, the files are automatically moved from ASP.NET temp to the Async Upload temporary folder, which is most commonly App_Data/RadUploadTemp. This temp folder can be set by the programmer to any folder on the system.To sum up, as the ASP.NET runtime intercepts the request, it uses the ASP.NET Temp folder in order to assemble the files there, and upon upload completion the latter are moved to the temporary folder.
In contrast, we have designed the Silverlight upload in a different way.The Silverlgiht module is designed from scratch to handle very large file uploads; on the client it divides the file to be uploaded in many chunks, each of which is 2mb large. It then starts uploading the chunks one after another and manually assembling them inside our temp folder (not the ASP.NET one).Dividing the file into chunks works around the large file uploads limitation in IIS. The size of the file to upload is only limited by the max file size allowed by the server’s operating system. Unfortunately, it is not possible to do that with IFrame/Flash because we have no control of the overall upload process.
|Upload Module||Browser Support|
|File Api||FireFox (3.6+), Chrome, Safari (5+), Opera, Safari for MAC|
In IE9 RadAsyncUpload implements only IFrame and Silverlight Upload modules. Flash module can be applied only in previous versions of IE Browser because of some incompatibilities with IE9.
In Lightweight render mode, RadAsyncUpload does not support Flash and Silverlight Upload modules.