The only solution I found is to store informations with
public override void ProcessRequest(System.Web.HttpContext context)
context.Session["persistance_test"] = "mydata";
BUT two questions still remain :
1) For a single file, the "normal" scenario for the RadUploadHandler is : receive the upload call, start with the firsts chunks, then continue the remaining chunks, then the final one, and then close the file.
Does this scenario can change ? (Does the order of the actions in the above scenario depends on the order of the received TCP packets - and can change if some TCP packet is dropped -, or can I assert that this order will ever be respected ?)
2) If I put the following session state parameters in my webconfig :
<sessionState mode="InProc" cookieless="true" timeout="2" /> (Session timeout = 2 minutes)
In the following cases, does the timeout (the sessionEnd event precisely) will be throwed before the end of the upload :
- If I upload multiple files, and the total upload time is estimated above 2 minutes ?
- If I upload a single file, and the total upload time is estimated above 2 minutes ?
Thanks in advance.