asp.net - Async/Await vs TPL vs WCF Service vs Web API: So many choices -


my asp.net 4 web app calls code spawns process long running script. standard output read , returned value updated in database. "fire , forget" bit of code ui remains responsive , user doesn't have wait around these 2 operations complete. end result of these 2 operations not needed calling code don't think need "await" , don't need indication of success or failure.

i'm getting confused of available options. best way code these 2 operations sent off on merry way , thing on own?

well, "best way" may debatable, proceed tpl using following:

task parenttask = task.factory.startnew(() => somemethod(someparameter)); 

note: if “long running script” calls wcf service, following article on wcf asynchronous programming may helpful. http://blogs.msdn.com/b/wenlong/archive/2009/02/09/scale-wcf-application-better-with-asynchronous-programming.aspx


Comments

Popular posts from this blog

c++ - OpenCV Error: Assertion failed <scn == 3 ::scn == 4> in unknown function, -

php - render data via PDO::FETCH_FUNC vs loop -

The canvas has been tainted by cross-origin data in chrome only -