Home/ Questions/Q 6840259
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T23:49:15+00:00

I’m aware of the model that involves a scheduled task runninng in the back

  • 0

I’m aware of the model that involves a scheduled task runninng in the back ground which runs jobs registered with a web request but how about this for an idea that keeps everything within ASP.net…

  1. User uploads a CSV file with, perhaps, several thousand rows. The rows are persisted to the database. I think this would take maybe a minute or so which would be an acceptable wait.

  2. Request returns to the browser and then an automatic Ajax request would go back to the server and request, say, ten rows at a time and process them. (Each row requires a number of web service requests.)

  3. Ajax call returns, display is updated and then another automatic Ajax request goes back for more rows. This repeats until all rows are completed.

  4. If user leaves the web page, then they could return and restart the job.

Any thoughts?

Cheers, Ian.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If i get you right, you actually dont need any “interaction” between background jobs and the long-running request, you just want to “lauch” background jobs with incoming requests? Not such a good idea. Take a look at the Quartz.NET project, it is scheduler embeddable into ASP.NET application, it will handle this stuff for you without need of requests. Of course, if there is app pool shutdown, also your scheduler goes down, but this you cant guarantee not to happen even with your long-running requests solution, dependent on browser waiting on other side.

    Also take a look on this interesting article from phil haack on this topic, with his own little scheduler library specific for ASP.NET :

    http://haacked.com/archive/2011/10/16/the-dangers-of-implementing-recurring-background-tasks-in-asp-net.aspx

    • 0