Sometimes a server-side operation, which is initiated via a callback request sent by the ASPxCallback control, may take much time (for instance, when a lot of data is obtained and being processed on the server). This example illustrates how you can inform your users about the server-side processing progress.
Note that this approach does not work if the Session state is used. It blocks parallel execution and forces parallel requests to be executed one after another because the access to ASP.NET Session state is exclusive per session.
Refer to the KA18599: How to perform parallel callbacks to get some information about server-side process KB Article for explanation.
See also:
How to display progress information about server-side callback processing (MVC)
How to track progress of server side processing on the client side (using HttpHandler)
How to track progress of server side processing on the client side (using HttpModule)
How to track progress of server side processing on the client side (using WebMethods)
Question Comments
Added By: David Geers at: 3/22/2013 2:48:15 PM
The "static double progress" field cannot be used. It is shared by all client running in the browser.
Open the demo in two browsers, say firefox and safari, run the first one, and then while it is running start the second one. The progress in the first windows will be reset to 0%.
This demo is totally useless.
Added By: Ken Tittle at: 4/30/2013 5:10:09 PMYup, this leads people down the wrong path. I'm trying to find an alternative though and can't seem to find it. It would be nice to store it in the Session object, but since EnableSessionState must be disabled, that can't happen. If anybody has an alternative, please let us know.
