How do I put following scenario into practice?

Question

0.00/5 (No votes)

See more:

SO. I am developing an application where I need to make long run Actions which proven to take more than 30k ms per request as I tested it. It does some API Calls to third party servers and return data in Json and Image formats.
Throughout searching SO questions and many other blog posts regarding the issue I have found out to have only two options.
1st. To make the Action return a partial view and render it on the main view showing some fancy loading gifs until the action progress is completed.
2nd. Have to write API Controllers and do the background work there.

What is the best choice between these two solutions and is there any other technique that I missed and deal with the situation better?
Thanks

What I have tried:

I am just reading blogs about Web APIs and related things

Posted 15-Feb-17 8:31am

Barcelonista Naser

Updated 16-Feb-17 4:59am

Add a Solution

2 solutions

Solution 1

You could try using a BackgroundWorker thread to execute the long running process and use ReportProgress to send progress back to your main thread. The Background thread will send a callback when it's completed. Your main thread would then be primarily responsible for running "fancy loading gifs" and the GUI.

Posted 16-Feb-17 4:42am

SteveHolle

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Accepted Answer · 2017-02-16T04:59:00

Any solution you implement that uses IIS is going to be at the mercy of IIS shutting down your app if it uses too much memory etc. You could farm the work off to a Windows Service, maybe using MSMQ to send the requests to the service, with the service doing all the actual work, and providing a mechanism where the front end can be informed of progress.