RadAsyncUpload

Keep in mind that RadAsyncUpload:
 Files are not directly uploaded to the page, but to a handler -Telerik.Web.UI.WebResource.axd.
 Uploaded files will be transferred to the TargetFolder when a postback occurs(meaning that you will
need to add a "Submit" button, so that the files will be saved in the target folder).
 The page submission is not automatically blocked until the file upload completes.
 Uploaded files are stored in a temporary location -App_Data/RadUploadTemp by default.
 Windows and Forms Authentication require special handling.

 

RadAsyncUploadutilizes three different modules for file uploading – Iframe, Flashand Silverlight. The module
with highest priority is Silverlight. If there 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:
1. How the IFrame/Flash modulehandles file uploads
The IFrame and Flash modules upload the selected file(s) using normal http post request. The iframe ues
tag for file uploads whereas Flash uses the Flex FileReference object in order to upload files. The files are
uploaded using Post HTTP request in absolutely the same manner as the normal and html form. On the
server, there is no difference where you have used the normal 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.
2. How the Silverlight modulehandles file uploads
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