Async Task<ActionResult> vs ActionResult

Question

0.00/5 (No votes)

See more:

Hi,
i'm new to MVC (nooob), and following MS Tutorial, and its just introduced async Task<actionresult> and shows the benefits. Does it mean that you should use async Task all the time rather than the normal ActionResult, (which is how it started the tutorial).

If async tasks<actionresult> speed up the performance etc, shouldn't these always be used?

I asked my fellow programmers and they've never seen it done this way so i thought id ask the trusty minds of Code Project.

and i'm assuming i'd still need to use Ajax requests in the future, as the ActionResults are only using for loading each individual page, the actions within the page will be ran using Ajax requests.?

Posted 4-Dec-14 23:42pm

Grant Weatherston

Updated 4-Dec-14 23:43pm

v2

Add a Solution

1 solution

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)

Jameel VM · Accepted Answer · 2014-12-05T00:19:00

Responsiveness is the main advantage of Async. Ajax async is related with the client(browser) and async Action Result is related with the server.
Why Asynchronous?

With today’s application’s growing more and more connected and also potentially long running tasks or blocking operations such as Network I/O or Database Operations.So it’s very important to hide the latency of these operations by starting them in background and returning back to the user interface quickly as possible. Here Asynchronous come in to the picture, Responsiveness

For speed up the performance you should continue with Parallel Programming

Why Parallel programming?
With today’s data sets growing larger and computations growing more complex. So it’s very important to reduce the execution time of these CPU-bound operations, in this case, by dividing the workload into chunks and then executing those chunks simultaneously. We can call this as “Parallel” .Obviously it will give high performance to our application.

Hope this helps