3 Answers, 1 is accepted
Thank you for contacting Telerik Support.
Straight to the point. This could be done by overriding the AddCacheDependency of the uploading handler.
I will be glad to assist you further.
Regards,
Peter Filipov
Telerik
Can you add this feature into a simple configuration property in future release? This would come in handy to allow the AsynchUpload to be used 24/7 and also share application pools with other apps.
Please point to a how-to page to override this. Thanks.
Thank you for the provided feedback. We have an initiative during the current release cycle to improve our "How To" section. We will discuss your suggestion and document it.
Regards,
Peter Filipov
Telerik
When RemovedCallback() is called, is the implementation of that routine deleting the temp file?
What if I still want to rely on the maximum temp file time, but not based on application pool recycle?
Is the reason different between Expired vs application pool recycle, so we can still retain the max temp file time?
Hi Peter,
The RemovedCallback() routine is tied to the AddCacheDependency method, and it's designed to manage the deletion of temporary files after a specified time interval. To keep temporary files beyond this interval without relying on application pool recycle, you could override the AddCacheDependency method and omit the CacheItemRemovedCallback, thus altering the default behavior for temporary file removal. This way, even if an application pool recycle occurs, your files remain unaffected until the maximum temp file time elapses. You can find more information in this article: How to Create a Custom Handler for RadAsyncUpload.