I had to replace the RadUpload controls in my app with RadAsyncUpload versions rather quickly and I may have missed out on a few details.
In my old system (while using RadUpload) I had code to delete the uploaded files once processed (inserted into a database field).
It looks to me like the simplest thing to do with the RadAsyncUpload would be to leave the files alone and rely on the control's TemporaryFileExpiration setting to do the job.
My question is this. Am I missing anything? Is there any real drawback to using the default App_Data\RadUploadTemp path and relying on automatic deletion of these temp files? (In fact, why should I even need a Target Folder?)
In my old system (while using RadUpload) I had code to delete the uploaded files once processed (inserted into a database field).
It looks to me like the simplest thing to do with the RadAsyncUpload would be to leave the files alone and rely on the control's TemporaryFileExpiration setting to do the job.
My question is this. Am I missing anything? Is there any real drawback to using the default App_Data\RadUploadTemp path and relying on automatic deletion of these temp files? (In fact, why should I even need a Target Folder?)