Discussion: the work of the web application after the session is closed. Means and opportunities?

Question

.NET

Good afternoon, I was inspired to create this topic by the need to continue the application after the session ends: when 1) the option with increasing session timeout is excluded, and 2) converting the plugin to a project using the workflow foundation technology is not always justified (since requests can be - both long in execution time and very fast).
Therefore, the possibilities, means, ideas about the implementation of the approach are very interesting, in which it is possible to untie the logic of request execution from the session by time limit.
The current idea, or rather its outline:
the separation of logic and layout. Required: authorization data and application code.
There is a timer, which is stored outside the application, and keeps track of the current session.
After the expiration of time - transfers control to the auxiliary. an application/service that accepts the intermediate results of a calculation up to that point in time and continues with the next calculation.
Completely received result is transferred to imposition.
So far, there are 2 ideas for finding a solution by features: 1) web-config; 2) iis, add-ons over iis.

Answer 1

An obvious solution suggests itself with a queue where the webapp throws off the task, a separate service that rakes this queue and puts the result of the work in the database / storage / cache. The webapp periodically polls the result, if there is one, it displays it on the page.

Answer 2

That is, the thread queue will be implemented in a web service - * .asmx inside the application, which receives data from the application, works with the queue, and upon completion - displays the result of the calculation of the thread (or a link to the final html)?