Does anyone have any comments on running an Action Handler asynchronously? I have a long running task which I'd like to run in the "background". At the moment the process it quite time consuming and doesn't provide a very good user experience. I guess I could move the process to a scheduled task. Anyone ever done this?
I have a task run async from an action handler. The problem is you loose context of the current session, thus, you can not publish documents, etc. There are ways around it, such as setting the publish at to publish immediately, or as slace pointed out, create a HttpHandler or Web Service to handle some of the task (as the http context is added back into the mix).
I think this should be reported as a bug, as the context should not be necessary in these cases, imo.
IActionHandler run Asynchronously
Does anyone have any comments on running an Action Handler asynchronously? I have a long running task which I'd like to run in the "background". At the moment the process it quite time consuming and doesn't provide a very good user experience. I guess I could move the process to a scheduled task. Anyone ever done this?
Action handlers aren't designed to be run in asyn, you'd be best having your action handler invoke a httpHandler, or fire off on a different thread.
HttpHandler would be my preferred option, as it is easier to debug ;)
I have a task run async from an action handler. The problem is you loose context of the current session, thus, you can not publish documents, etc. There are ways around it, such as setting the publish at to publish immediately, or as slace pointed out, create a HttpHandler or Web Service to handle some of the task (as the http context is added back into the mix).
I think this should be reported as a bug, as the context should not be necessary in these cases, imo.
Case
is working on a reply...